From: Jeff Garzik <jgarzik@pobox.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: devinit
Date: Wed, 06 Aug 2003 19:21:23 -0400 [thread overview]
Message-ID: <3F318D73.3000809@pobox.com> (raw)
In-Reply-To: <20030806230919.GB8187@kroah.com>
Greg KH wrote:
> I've applied the 2.6 patch to my trees and will send it on to Linus in a
> few days, thanks.
Speaking of PCI... are we gonna have to zap __devinit too? Another
option is to think of add-new-pci-ids-on-the-fly as a CONFIG_HOTPLUG
feature, which should(?) maintain the current __devinit semantics: no
re-probes.
OTOH, __devinit already is a no-op for CONFIG_HOTPLUG cases (read: most
everybody), so I wonder if we care enough about __devinit anymore? I
used the same logic to support __devinitdata removal, after all.
Jeff
next prev parent reply other threads:[~2003-08-06 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 19:54 [PATCH] trivial 2.4/2.6 PCI name change/addition Alex Williamson
2003-08-06 22:13 ` Bjorn Helgaas
2003-08-07 12:05 ` Marcelo Tosatti
2003-08-07 12:32 ` Marcelo Tosatti
2003-08-07 15:52 ` Bjorn Helgaas
2003-08-06 23:09 ` Greg KH
2003-08-06 23:21 ` Jeff Garzik [this message]
2003-08-06 23:31 ` devinit Greg KH
2003-08-07 20:26 ` devinit Tom Rini
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=3F318D73.3000809@pobox.com \
--to=jgarzik@pobox.com \
--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