Date: Sat, 16 Aug 2003 13:09:38 +0200
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
Message-ID: <20030816130938.H670@nightmaster.csn.tu-chemnitz.de>
References: <20030815182459.GA3755@kroah.com> <20030815215459.Y639@nightmaster.csn.tu-chemnitz.de> <20030816032833.GA6680@kroah.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20030816032833.GA6680@kroah.com>; from greg@kroah.com on Fri, Aug 15, 2003 at 08:28:33PM -0700
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1707
Lines: 51

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/