From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Bartlomiej Zolnierkiewicz <dake@staszic.waw.pl>
Cc: "Adam J. Richter" <adam@yggdrasil.com>, linux-kernel@vger.kernel.org
Subject: Re: Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compilefailure
Date: Tue, 14 Nov 2000 18:01:25 -0500 [thread overview]
Message-ID: <3A11C445.EB65B9D@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011142345440.2383-100000@tricky>
Bartlomiej Zolnierkiewicz wrote:
>
> On Mon, 13 Nov 2000, Adam J. Richter wrote:
>
> > linux-2.4.0-test11-pre4/drivers/sound/yss225.c uses __initdata
> > but does not include <linux/init.h>, so it could not compile. I have
> > attached below.
> >
> > Note that I am a bit uncertain about the correctness of
> > the __initdata prefix here in the first place. Is yss225 a PCI
> > device? If so, a kernel that supports PCI hot plugging should
> > be prepared to support the possibility of a hot pluggable yss225
> > card being inserted after the module has already been initialized.
> > Even if no CardBus or CompactPCI version of yss225 hardware exists
> > yet, it will require less maintenance for PCI drivers to be prepared
> > for this possibility from the outset (besides, is it possible to have a
> > hot pluggable PCI bridge card that bridges to a regular PCI bus?).
>
> Good question....
Please err on the conservative side -- IMHO you shouldn't mark a driver
as hotpluggable (by using the '__dev' prefix) unless you know it is
necessary.
Otherwise, you rob CONFIG_HOTPLUG people of some memory that could
otherwise be freed at boot. And the number of CONFIG_HOTPLUG people is
not small, it includes not only the CardBus users but USB users too...
Jeff
--
Jeff Garzik |
Building 1024 | The chief enemy of creativity is "good" sense
MandrakeSoft | -- Picasso
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-14 23:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 22:44 Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compile failure Adam J. Richter
2000-11-14 22:56 ` Bartlomiej Zolnierkiewicz
2000-11-14 23:01 ` Jeff Garzik [this message]
2000-11-14 23:17 ` Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compilefailure Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2000-11-15 1:02 Adam J. Richter
2000-11-15 5:29 ` Jeff Garzik
2000-11-15 5:43 ` Greg KH
2000-11-15 5:54 ` Jeff Garzik
2000-11-15 6:52 ` Greg KH
2000-11-15 7:58 Adam J. Richter
2000-11-15 8:32 Adam J. Richter
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=3A11C445.EB65B9D@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=adam@yggdrasil.com \
--cc=dake@staszic.waw.pl \
--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.