public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Adam Belay <abelay@novell.com>
Cc: Andrew Morton <akpm@osdl.org>,
	perex@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/pnp/: possible cleanups
Date: Sat, 12 Mar 2005 18:07:06 +0100	[thread overview]
Message-ID: <20050312170706.GF3814@stusta.de> (raw)
In-Reply-To: <1110588297.12485.251.camel@localhost.localdomain>

On Fri, Mar 11, 2005 at 07:44:56PM -0500, Adam Belay wrote:
> On Fri, 2005-03-11 at 16:23 -0800, Andrew Morton wrote:
> > Adam Belay <abelay@novell.com> wrote:
> > >
> > > 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?
> > 
> > You're the maintainer...
> 
> I've been holding off on making many changes to PnP at the moment,
> because I have been considering replacing it with a new (more modern and
> ACPI capable) ISA/LPC bridge driver.  This work would likely begin after
> my PCI bridge driver rewrite is finished and merged (as the PCI work is
> in some ways a prerequisite).
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=111023821617705&w=2
> 
> Still, if there are changes to fix actual bugs, then I'm all for them.
> 
> Also a few features could be added.  Specifically PnPBIOS
> hotplug/docking station support.  If anyone's interested, I may
> implement it (and it would use some functions that were removed by this
> patch).  Furthermore, ISAPnP could be made a module.  PnPBIOS probably
> couldn't.
>...

Note that my 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.

> Thanks,
> Adam

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2005-03-12 17:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 18:16 [2.6 patch] drivers/pnp/: possible cleanups 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 [this message]
  -- 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=20050312170706.GF3814@stusta.de \
    --to=bunk@stusta.de \
    --cc=abelay@novell.com \
    --cc=akpm@osdl.org \
    --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