From: Adam Belay <abelay@novell.com>
To: Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>
Cc: perex@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/pnp/: possible cleanups
Date: Fri, 11 Mar 2005 19:02:42 -0500 [thread overview]
Message-ID: <1110585763.12485.223.camel@localhost.localdomain> (raw)
In-Reply-To: <20050311181606.GC3723@stusta.de>
This patch essential makes it impossible for PnP protocols to be
modules. Currently, they are all in-kernel. If that is acceptable...,
then this patch looks fine to me. Any comments?
Thanks,
Adam
On Fri, 2005-03-11 at 19:16 +0100, Adrian Bunk wrote:
> This patch contains the following possible cleanups:
> - make needlessly global code static
> - #if 0 the following unused global function:
> - core.c: pnp_remove_device
> - remove the following unneeded EXPORT_SYMBOL's:
> - card.c: pnp_add_card
> - card.c: pnp_remove_card
> - card.c: pnp_add_card_device
> - card.c: pnp_remove_card_device
> - card.c: pnp_add_card_id
> - core.c: pnp_register_protocol
> - core.c: pnp_unregister_protocol
> - core.c: pnp_add_device
> - core.c: pnp_remove_device
> - pnpacpi/core.c: pnpacpi_protocol
> - driver.c: pnp_add_id
> - isapnp/core.c: isapnp_read_byte
> - manager.c: pnp_auto_config_dev
> - resource.c: pnp_register_dependent_option
> - resource.c: pnp_register_independent_option
> - resource.c: pnp_register_irq_resource
> - resource.c: pnp_register_dma_resource
> - resource.c: pnp_register_port_resource
> - resource.c: pnp_register_mem_resource
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
next prev parent reply other threads:[~2005-03-12 0:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 18:16 Adrian Bunk
2005-03-12 0:02 ` Adam Belay [this message]
2005-03-12 0:23 ` Andrew Morton
2005-03-12 0:44 ` Adam Belay
2005-03-12 0:46 ` Adam Belay
2005-03-12 17:07 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2005-05-17 0:08 Adrian Bunk
2005-05-17 0:35 ` Adam Belay
2005-05-02 1:46 Adrian Bunk
2005-02-27 0:52 Adrian Bunk
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=1110585763.12485.223.camel@localhost.localdomain \
--to=abelay@novell.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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
Powered by JetHome