Date: Tue, 1 Mar 2005 12:45:11 -0800
From: Greg KH <greg@kroah.com>
To: Valdis.Kletnieks@vt.edu, Andrew Morton <akpm@osdl.org>,
       linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-rc5-mm1
Message-ID: <20050301204509.GH23484@kroah.com>
References: <20050301012741.1d791cd2.akpm@osdl.org> <200503011336.j21DaaqC008164@turing-police.cc.vt.edu> <20050301135529.A1940@flint.arm.linux.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050301135529.A1940@flint.arm.linux.org.uk>
User-Agent: Mutt/1.5.8i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1963
Lines: 45

On Tue, Mar 01, 2005 at 01:55:29PM +0000, Russell King wrote:
> On Tue, Mar 01, 2005 at 08:36:36AM -0500, Valdis.Kletnieks@vt.edu wrote:
> > On Tue, 01 Mar 2005 01:27:41 PST, Andrew Morton said:
> > > 
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc5/2.6.11-rc5-mm1/
> > 
> > > - A pcmcia update which obsoletes cardmgr (although cardmgr still works) and
> > >   makes pcmcia work more like regular hotpluggable devices.  See the
> > >   changelong in pcmcia-dont-send-eject-request-events-to-userspace.patch for
> > >   details.
> > 
> > This is still showing the same 'cs: unable to map card memory!' issue on my
> > Dell laptop.  Backing out bk-pci.patch makes it work again.
> > 
> > For what it's worth, the hotplug system wasn't able to initialize the wireless
> > card (TrueMobile 1150) at boot - still needed cardmgr to get it started up.
> > But that might just me being an idiot...
> 
> It's probably a clash between the PCI updates and the PCMCIA updates.
> 
> The PCI updates change the prototype of a helper function for 
> pci_bus_alloc_resource(), but don't touch the actual helper function
> in PCMCIA.
> 
> This means that the PCI update is actually broken - if it's merged as
> is into Linus' tree, PCMCIA will break there as well.
> 
> Can whoever did the PCI update please resolve this mismatch.  Moreover,
> if 2.6.11 appears, please do not merge the PCI updates until this has
> been resolved.  Thanks.

Andrew had a stale bk-pci tree in his local copy, and that is where that
change came from.  It will not show up in the next -mm release, and will
not be sent to Linus until after I have fixed up the _whole_ tree.

So sorry for the inconvience.

thakns,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/