On Sun, 11 Mar 2007 13:55:54 MDT, Eric Moore said:Certainly appropriate content for something on your website, and vendors who provide programs like dmidecode and parsemce are always welcome. I could probably be convinced that such info should have at least a pointer somewhere in Documentation/lsi_debug.txt or some such. But quite frankly, if I'm reduced to wading through *.h files to figure out what some recalcitrant hardware is upset about, there's been a failure in documentation. *ESPECIALLY* if I go look at drivers/whatever/source.c and it doesn't even *reference* the *.h file in question. Feel free to include mpi_inb.h when you submit the interface for merging.
| Hiten Pandya | Re: up? (emacs docbook xml ide) |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Ingo Molnar | iwlwifi: fix build bug in "iwlwifi: fix LED stall" |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
