public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, pcihpd-discuss@lists.sourceforge.net
Subject: Re: [PATCH] PCI and PCI Hotplug changes and fixes for 2.5.70
Date: Thu, 5 Jun 2003 18:57:12 +0100	[thread overview]
Message-ID: <20030605185712.B4125@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030605170410.GA5284@kroah.com>; from greg@kroah.com on Thu, Jun 05, 2003 at 10:04:10AM -0700

On Thu, Jun 05, 2003 at 10:04:10AM -0700, Greg KH wrote:
> On Thu, Jun 05, 2003 at 10:19:36AM +0100, Russell King wrote:
> > On Wed, Jun 04, 2003 at 07:05:47PM -0700, Greg KH wrote:
> > > diff -Nru a/drivers/pci/bus.c b/drivers/pci/bus.c
> > > --- a/drivers/pci/bus.c	Wed Jun  4 18:11:51 2003
> > > +++ b/drivers/pci/bus.c	Wed Jun  4 18:11:51 2003
> > > @@ -129,6 +129,5 @@
> > >  	}
> > >  }
> > >  
> > > -EXPORT_SYMBOL(pci_bus_alloc_resource);
> > >  EXPORT_SYMBOL(pci_bus_add_devices);
> > >  EXPORT_SYMBOL(pci_enable_bridges);
> > 
> > Please don't remove this one.  Its there for stuff like:
> > 
> > drivers/pcmcia/cardbus.c
> 
> Sorry, I don't see that in the current kernel version of cardbus.c,
> otherwise I would not have moved it out.  Feel free to put it back, if
> you need it for any future cardbus changes.

Well, if people are going to remove stuff, I'm not going to be bothered
to even submit the changes.  I've got enough to do at the moment to go
around putting stuff back into the kernel which I've already submitted.

> /*
>  * This file is going away.  Cardbus handling has been re-written to be
>  * more of a PCI bridge thing, and the PCI code basically does all the
>  * resource handling. This has wrappers to make the rest of the PCMCIA
>  * subsystem not notice that it's not here any more.
>  *
>  *              Linus, Jan 2000
>  */
> 
> Is that ever going to happen?  Just curious, because if so, I can remove
> some more functions from pci.h :)

It doesn't look like it.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-06-05 17:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05  1:31 [BK PATCH] PCI and PCI Hotplug changes and fixes for 2.5.70 Greg KH
2003-06-05  2:05 ` [PATCH] " Greg KH
2003-06-05  2:05   ` Greg KH
2003-06-05  2:05     ` Greg KH
2003-06-05  2:05       ` Greg KH
2003-06-05  2:05         ` Greg KH
2003-06-05  2:05           ` Greg KH
2003-06-05  2:05             ` Greg KH
2003-06-05  2:05               ` Greg KH
2003-06-05  2:05                 ` Greg KH
2003-06-05  2:05                   ` Greg KH
2003-06-05  2:05                     ` Greg KH
2003-06-05  9:19                 ` Russell King
2003-06-05 17:04                   ` Greg KH
2003-06-05 17:57                     ` Russell King [this message]
2003-06-05  2:14 ` [BK PATCH] " Greg KH
2003-06-05  8:38   ` Dave Jones
2003-06-05  8:49     ` Greg KH
2003-06-05  8:59       ` Dave Jones
2003-06-05  9:06         ` Greg KH
2003-06-05  9:18           ` Dave Jones
2003-06-05  9:22             ` Russell King
2003-06-05 17:18             ` Greg KH
2003-06-05 19:10               ` Dave Jones

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=20030605185712.B4125@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    /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