From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] Driver Core fixes for 2.6.0-test3
Date: Sat, 16 Aug 2003 13:09:38 +0200 [thread overview]
Message-ID: <20030816130938.H670@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20030816032833.GA6680@kroah.com>; from greg@kroah.com on Fri, Aug 15, 2003 at 08:28:33PM -0700
Hi,
On Fri, Aug 15, 2003 at 08:28:33PM -0700, Greg KH wrote:
> On Fri, Aug 15, 2003 at 09:54:59PM +0200, Ingo Oeser wrote:
[...]
> Hi, I've brought this back to lkml as I'm getting tired of private email
> threads about this topic. Hope you don't mind.
I don't.
> > On Fri, Aug 15, 2003 at 11:25:00AM -0700, Greg KH wrote:
> > > Here's some driver core changes that do the following things:
> > > - remove struct device.name field and fix up remaining
> > > subsystems
> >
> > Could you point me to the rationale about this?
> >
> > I for one considered "everything should have a name" policy very
> > useful and extendible.
> Naming databases belong in userspace. For PCI, PnP, and USB we can
> determine the name ourselves from userspace using lspci, lspnp, and
> lsusb. Getting rid of the name field prevents us from relying on kernel
> code when we shouldn't be.
lspci at least shows only name OR number, but never both
together.
So that this tool is not very useful for name resolving in case
of problems, because you have no simple way to match your input
with its output. But don't worry, M$ does the same UI mistake and
this can be easily fixed.
But this shifting is a good reason. This also helps the "product
and company changing names" disease ;-)
> Hey, we're saving kernel memory, and this is a problem? :)
;-)
> Hope this helps explain things.
Explains exactly what I liked to know.
Many thanks and regards
Ingo Oeser
prev parent reply other threads:[~2003-08-16 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 18:25 Greg KH
2003-08-15 18:25 ` [PATCH] " Greg KH
2003-08-15 18:25 ` Greg KH
2003-08-15 18:25 ` Greg KH
2003-08-15 18:25 ` Greg KH
2003-08-15 18:25 ` Greg KH
2003-08-15 18:25 ` Greg KH
2003-08-15 18:25 ` Greg KH
[not found] ` <20030815215459.Y639@nightmaster.csn.tu-chemnitz.de>
2003-08-16 3:28 ` [BK PATCH] " Greg KH
2003-08-16 11:09 ` Ingo Oeser [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030816130938.H670@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®