public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: alan@lxorguk.ukuu.org.uk, greg@kroah.com, jung-ik.lee@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: Patch: 2.5.45 PCI Fixups for PCI HotPlug
Date: Mon, 04 Nov 2002 15:44:35 -0500	[thread overview]
Message-ID: <3DC6DC33.1010509@pobox.com> (raw)
In-Reply-To: 200211042029.MAA09749@adam.yggdrasil.com

Adam J. Richter wrote:

>	Jeff Garzik recently said that he doesn't want to incorporate
>hot plugging for arbitrary standard PCI cards until he hears about a
>hotplug configuration that uses that card (I'm cc'ing Jeff so he can
>correct me if I misunderstand). That would put the kernel at level 1
>in the above list.
>

No, I was talking more specifically about de2104x driver.

For general drivers I prefer __devinit out of general laziness:  if 
there is not an active and kernel-clueful maintainer, then it's better 
to mark everything __devinit [with the wastage it implies].  But for a 
few drivers with obviously provable/disprovable cases, __init may be better.

So it IMO matters WRT maintainer and testability issues as well as 
strictly kernel/technical issues.

    Jeff





  reply	other threads:[~2002-11-04 20:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 20:29 Patch: 2.5.45 PCI Fixups for PCI HotPlug Adam J. Richter
2002-11-04 20:44 ` Jeff Garzik [this message]
2002-11-05 13:01 ` Ivan Kokshaysky
  -- strict thread matches above, loose matches on Subject: below --
2002-11-06  0:14 Adam J. Richter
2002-11-05 13:17 Adam J. Richter
2002-11-05 15:28 ` Ivan Kokshaysky
2002-11-04 18:23 Adam J. Richter
2002-11-04 19:05 ` Alan Cox
2002-11-04 18:06 Lee, Jung-Ik
2002-11-03 12:31 Adam J. Richter
2002-11-03  0:56 Lee, Jung-Ik
2002-11-03  7:58 ` Greg KH

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=3DC6DC33.1010509@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=adam@yggdrasil.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=jung-ik.lee@intel.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