LKML Archive on
help / color / mirror / Atom feed
From: Greg KH <>
To: Jonas Bonn <>
Subject: Re: pci_device_id definition cleanups
Date: Fri, 15 Feb 2008 16:05:12 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1203117700.16761.9.camel@satguru>

On Sat, Feb 16, 2008 at 12:21:40AM +0100, Jonas Bonn wrote:
> I've done some work on cleaning up the definitions of pci_device_id to
> make them "static const" (where possible) and to make sure they go into
> __devinitconst.  There are about 350 changes of the type shown in the
> diff at the end of this mail.
> ???All these changes are in my public GIT tree at:
> git://
> (Based on 2.6.25-rc2)
> In addition to these pci_device_id changes, there are a few changesets
> that move "const" data from __devinitdata to __devinitconst.
> The tree above builds with both allmodconfig and allyesconfig.

Hm, does this save us any memory on any type of configuration?

What about drivers that end up writing to these structures (I know some
USB drivers do, not sure about PCI ones.)

You're going to need to send out patches for these to the different
developers, a git tree isn't going to help much.


greg k-h

  reply	other threads:[~2008-02-16  0:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 23:21 Jonas Bonn
2008-02-16  0:05 ` Greg KH [this message]
2008-02-16  0:55   ` Jeff Garzik
2008-02-16  0:57     ` Greg KH
2008-02-16  2:23 ` Sam Ravnborg
2008-02-16  5:27   ` Olof Johansson
2008-02-16 12:24     ` Sam Ravnborg

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: pci_device_id definition cleanups' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).