[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080408202003.GJ11962@parisc-linux.org>
Date: Tue, 8 Apr 2008 14:20:04 -0600
From: Matthew Wilcox <matthew@....cx>
To: Dan Noe <dpn@...merica.net>
Cc: Ingo Molnar <mingo@...e.hu>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
"Kok, Auke-jan H" <auke-jan.h.kok@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
NetDev <netdev@...r.kernel.org>,
e1000-list <e1000-devel@...ts.sourceforge.net>,
linux-pci maillist <linux-pci@...ey.karlin.mff.cuni.cz>,
Jeff Garzik <jeff@...zik.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"David S. Miller" <davem@...emloft.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Ronciak, John" <john.ronciak@...el.com>,
"Allan, Bruce W" <bruce.w.allan@...el.com>,
Greg KH <greg@...ah.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [regression] e1000e broke e1000
On Tue, Apr 08, 2008 at 04:12:29PM -0400, Dan Noe wrote:
> It would be nice if lspci could display what driver had claimed a
> particular device
You need to upgrade to a more recent version of lspci -- it already does
this ;-)
Maybe 'status' would be a better name than 'broken'. We could even
default it to 'unclaimed' then. Or 'driver_status' to avoid conflicting
with some bus that might have a 'status' bit we try to report through
sysfs.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists