mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
	perex@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/pnp/: possible cleanups
Date: Mon, 16 May 2005 20:35:25 -0400	[thread overview]
Message-ID: <20050517003525.GB11189@neo.rr.com> (raw)
In-Reply-To: <20050517000853.GN5112@stusta.de>

On Tue, May 17, 2005 at 02:08:53AM +0200, Adrian Bunk wrote:

Hi Adrian,

I'll apply this patch if you comment out or use "#if 0" on the exported
symbols.  Also do not remove isapnp_read_byte or pnp_auto_config_dev because
they are part of the device driver API.  I would like you to only target the
protocol API.  I'll have the time to seriously work on features like modular
isapnp in about a week.

Thanks,
Adam


> 
> 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
> 
> Note that this patch #if 0's exactly one functions and removes no
> functions. Most it does is the removal of EXPORT_SYMBOL's, so if any
> modular code will use any of them, re-adding will be trivial.
> 
> Modular ISAPnP might be interesting in some cases, but this is more
> legacy code. If someone would work on it to sort all the issues out
> (starting with the point that most users of __ISAPNP__ will have to be
> fixed) re-adding the required EXPORT_SYMBOL's won't be hard for him.
> 
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
> 
> ---

  reply	other threads:[~2005-05-17  0:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17  0:08 Adrian Bunk
2005-05-17  0:35 ` Adam Belay [this message]
2005-06-20 23:43   ` [2.6 patch] drivers/pnp/: cleanups Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2005-05-02  1:46 [2.6 patch] drivers/pnp/: possible cleanups Adrian Bunk
2005-03-11 18:16 Adrian Bunk
2005-03-12  0:02 ` Adam Belay
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
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=20050517003525.GB11189@neo.rr.com \
    --to=ambx1@neo.rr.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

all inboxes | Powered by JetHome®