public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert T. Johnson" <rtjohnso@eecs.berkeley.edu>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test6: a few __init bugs
Date: 30 Sep 2003 14:20:53 -0700	[thread overview]
Message-ID: <1064956854.5733.233.camel@dooby.cs.berkeley.edu> (raw)
In-Reply-To: <20030930191117.GA20054@kroah.com>

On Tue, 2003-09-30 at 12:11, Greg KH wrote:
> Hm, care to send in a patch that adds a comment to that __init call so
> that others don't make the same mistake in a year or so?

Here's the patch you requested, but I recommend against applying it
since it's the sort of comment that can easily become wrong, leading to
missed bugs in future kernels.  Thanks again for your help.

Best,
Rob

--- drivers/pci/quirks.c.orig	Tue Sep 30 14:17:40 2003
+++ drivers/pci/quirks.c	Tue Sep 30 14:16:57 2003
@@ -869,6 +869,9 @@
 
 void pci_fixup_device(int pass, struct pci_dev *dev)
 {
+	/* Note: Many of the hooks in pci_fixups are declared __init
+           or __devinit, but this is ok because, currently, none of
+           the devices with quirk hooks are hot-pluggable. */
 	pci_do_fixups(dev, pass, pcibios_fixups);
 	pci_do_fixups(dev, pass, pci_fixups);
 }



  parent reply	other threads:[~2003-09-30 21:21 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 [this message]
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=1064956854.5733.233.camel@dooby.cs.berkeley.edu \
    --to=rtjohnso@eecs.berkeley.edu \
    --cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox