From: Greg KH <greg@kroah.com>
To: "Robert T. Johnson" <rtjohnso@eecs.berkeley.edu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
scottm@somanetworks.com, rgooch@atnf.csiro.au, mingo@redhat.com,
pavel@suse.cz
Subject: Re: 2.6.0-test6: a few __init bugs
Date: Mon, 29 Sep 2003 15:11:13 -0700 [thread overview]
Message-ID: <20030929221113.GB2720@kroah.com> (raw)
In-Reply-To: <1064872693.5733.42.camel@dooby.cs.berkeley.edu>
On Mon, Sep 29, 2003 at 02:58:12PM -0700, Robert T. Johnson wrote:
> ** Possible bug:
> ** drivers/pci/quirks.c:asus_hides_smbus_hostbridge() (__init)
> in table: drivers/pci/quirks.c:pci_fixups (not __init)
> indirect call f->hook(): drivers/pci/quirks.c:pci_do_fixups() (not __init)
> called by: drivers/pci/quirks.c:pci_fixup_device() (not __init)
> called by: drivers/pci/probe.c:pci_scan_slot() (not __init)
> called by lots of hotplug enable() functions, e.g.
> drivers/pci/hotplug/ibmphp_core.c:ibm_configure_device() (not __init)
> called by drivers/pci/hotplug/ibmphp_core.c:enable_slot() (not __init)
>
> Note: It looks like this may have been originally designed to initialize the
> pci bus at startup, but has been re-used in the hotplug code, which means it
> can be run after the __init segments have gone away.
>
> Fix: Delete all the __init declarations on the quirks hooks.
No, this was discussed a lot a year or so ago. We don't currently have
anything in the quirks table that can be hotplug added as far as I know.
So it's safe for us to throw those quirk entries away.
Yeah, it doesn't make automated test tools easy for this case, sorry.
Hope this helps.
greg k-h
next prev parent reply other threads:[~2003-09-29 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 21:58 Robert T. Johnson
2003-09-29 22:07 ` Pavel Machek
2003-09-29 22:11 ` Greg KH [this message]
[not found] ` <1064946634.5734.106.camel@dooby.cs.berkeley.edu>
[not found] ` <20030930191117.GA20054@kroah.com>
2003-09-30 21:20 ` Robert T. Johnson
2003-09-30 21:25 ` Greg KH
2003-09-30 21:42 ` Robert T. Johnson
2003-09-30 22:10 ` Greg KH
2003-10-01 21:26 ` bill davidsen
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=20030929221113.GB2720@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@suse.cz \
--cc=rgooch@atnf.csiro.au \
--cc=rtjohnso@eecs.berkeley.edu \
--cc=scottm@somanetworks.com \
/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®