From: Greg KH <greg@kroah.com>
To: Adam Belay <ambx1@neo.rr.com>,
torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk,
jdthood@yahoo.co.uk, boissiere@nl.linux.org, perex@perex.cz,
jgarzik@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PnP Layer Rewrite V0.7 - 2.4.42
Date: Tue, 15 Oct 2002 13:32:50 -0700 [thread overview]
Message-ID: <20021015203250.GH15864@kroah.com> (raw)
In-Reply-To: <20021015160946.GD315@neo.rr.com>
On Tue, Oct 15, 2002 at 04:09:46PM +0000, Adam Belay wrote:
> > > +static const struct pnp_id pnp_dev_table[] = {
> > > + /* Standard LPT Printer Port */
> > > + { "PNP0400", 0 },
> >
> > Using named initializers are preferred.
>
> I'm not quite sure what you mean here.
Something like:
static const struct pnp_id pnp_dev_table[] = {
/* standard printer port */
{ .name = "PNP0400", .data = 0},
or whatever those fields are called.
> > pnp_register_driver() should be implemented so that you don't need a
> > #ifdef around it to call it. Put the #ifdef in the header file.
>
> Actually pnp_register_driver is implemented in this way. The reason it
> has #ifdef around it is becuase of the previous #ifdef statement
> (where parport_pc_pnp_driver is defined).
Removing #ifdefs is also nice :)
> Also I had a hotplug related question? Is it possible for pnp drivers
> to use this and if so what do I need to do?
>
> MODULE_DEVICE_TABLE(pnp, pnp_dev_table);
To fully support this, you need to modify modutils to generate the
proper modules.pnpmap file from the .o files. Take a look at the source
for it for how to do this.
Also, some kind of /sbin/hotplug notification when a pnp device is found
is a good idea. Hm, looks like you already get that for free right now
with the existing driver code, nevermind :)
thanks,
greg k-h
next prev parent reply other threads:[~2002-10-15 20:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021014135452.GB444@neo.rr.com>
2002-10-14 18:10 ` [PATCH] PnP Layer Rewrite V0.7 - 2.4.42 Greg KH
2002-10-15 16:09 ` Adam Belay
2002-10-15 20:32 ` Greg KH [this message]
2002-10-14 19:10 ` Jaroslav Kysela
2002-10-14 19:22 ` Jeff Garzik
2002-10-14 21:43 ` Adam Belay
2002-10-15 3:13 ` Greg KH
2002-10-15 15:36 ` Thomas Hood
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=20021015203250.GH15864@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ambx1@neo.rr.com \
--cc=boissiere@nl.linux.org \
--cc=jdthood@yahoo.co.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=torvalds@transmeta.com \
/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.