Re: [BK PATCH] Driver Core fixes for 2.6.0-test3

From: Ingo Oeser (ingo.oeser_at_informatik.tu-chemnitz.de)
Date: 08/16/03

  • Next message: Adam J. Richter: "Re: [RFC][PATCH] Make cryptoapi non-optional?"
    Date:	Sat, 16 Aug 2003 13:09:38 +0200
    To: Greg KH <greg@kroah.com>
    
    

    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/


  • Next message: Adam J. Richter: "Re: [RFC][PATCH] Make cryptoapi non-optional?"

    Relevant Pages

    • Re: Things that Longhorn seems to be doing right
      ... > Also keep in mind that Microsoft very deliberately blurs what they do ... > file metadata in a MySQL database which can be searched via ... > appropriate userspace libraries which we provide. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: AGP problem SiS 746FX Linux 2.6.5-rc3
      ... I actually had that in mind when I merged this code, ... Can you send lspci -n output please? ... send the line "unsubscribe linux-kernel" in ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: [1/1][PATCH] nproc v2: netlink access to /proc information
      ... > The presumed wrong assumptions underlying broken tools of the future ... > making it easy to write correct applications (or in fixing broken apps ... knowledge of the CONFIG_MMU usage models and/or whatever userspace ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: User space out of memory approach
      ... > userspace provided candidate list. ... > instead of fixing the real problem is a real interesting engineering ... that after the source of trouble is fixed it is worth to ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: finding out the value of HZ from userspace
      ... > When we go to a tickless kernel and offer high-resolution timers to ... is the value of HZ reported to userspace anywhere? ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)