public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] More PCI fixes for 2.6.0-test2
Date: Sat, 9 Aug 2003 10:07:14 -0700	[thread overview]
Message-ID: <20030809170714.GA7831@kroah.com> (raw)
In-Reply-To: <20030809091524.A13885@flint.arm.linux.org.uk>

On Sat, Aug 09, 2003 at 09:15:24AM +0100, Russell King wrote:
> On Fri, Aug 08, 2003 at 05:30:36PM -0700, Greg KH wrote:
> > Here are a few more fixes for the PCI core code for 2.6.0-test2-bk.
> > I've removed all of the struct device.name usages as that field is about
> > to go away, and there is a fix from Ivan in here too.
> 
> When was that decided?  I don't remember seeing any discussion, and since
> it affects more than PCI... Seems like a backwards step to me.

We discussed this at OLS/Kernel Summit.  I sure thought you were there
for that conversation.  The PnP, USB, I2C, and PCI core is already
cleaned up, with patches in 2.6.0-test3, and I have a patch around here
that fixes up the rest of the kernel (SCSI, PCMCIA, and then the driver
core.)  I'll send them out next week.

Basically, we don't want to be carrying around info if we don't really
need it (like the PCI names database.)  All of this info can already be
found from userspace programs, with a few exceptions.  I2C is one such
exception, so I've added the name back into the local structure (and
will export it to sysfs once the driver core 'name' file removal patch
is in.)   

This is a nice memory savings for the majority of the users of the
struct device structure.

thanks,

greg k-h

      reply	other threads:[~2003-08-09 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-09  0:30 [BK PATCH] More PCI fixes for 2.6.0-test2 Greg KH
2003-08-09  0:32 ` [PATCH] " Greg KH
2003-08-09  0:32   ` Greg KH
2003-08-09  0:32     ` Greg KH
2003-08-09  0:32       ` Greg KH
2003-08-09  8:15 ` [BK PATCH] " Russell King
2003-08-09 17:07   ` Greg KH [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=20030809170714.GA7831@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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