From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test6: a few __init bugs
Date: 1 Oct 2003 21:26:07 GMT [thread overview]
Message-ID: <blfgpf$j8d$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 1064958129.5264.237.camel@dooby.cs.berkeley.edu
In article <1064958129.5264.237.camel@dooby.cs.berkeley.edu>,
Robert T. Johnson <rtjohnso@eecs.berkeley.edu> wrote:
| On Tue, 2003-09-30 at 14:25, Greg KH wrote:
| > Hm, good point. Can you think of a better place for this that would
| > have helped you out?
|
| Take two. It might not have prevented me from reporting the potential
| bug, but I would've known you'd thought about it, it might help future
| developers, and it's unlikely to become dangerously wrong. Thanks.
|
| Best,
| Rob
|
| --- drivers/pci/quirks.c.orig Tue Sep 30 14:17:40 2003
| +++ drivers/pci/quirks.c Tue Sep 30 14:39:48 2003
| @@ -750,6 +750,9 @@
|
| /*
| * The main table of quirks.
| + *
| + * Note: any hooks for hotpluggable devices in this table must _NOT_
| + * be declared __init.
| */
|
| static struct pci_fixup pci_fixups[] __devinitdata = {
Good job, that. Clear, and anyone who doesn't immediately see why
probably is at a skill level to just say 'oh' and do what it says.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
prev parent reply other threads:[~2003-10-01 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 21:58 2.6.0-test6: a few __init bugs Robert T. Johnson
2003-09-29 22:07 ` Pavel Machek
2003-09-29 22:11 ` Greg KH
[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 [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='blfgpf$j8d$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.