Re: 2.6.12-7 upload ? How far away is 2.6.13-1 ?
On Wed, Sep 21, 2005 at 12:20:46PM +0900, Horms wrote:
> On Tue, Sep 20, 2005 at 01:08:36PM +0200, Sven Luther wrote:
> > On Tue, Sep 20, 2005 at 07:27:46PM +0900, Horms wrote:
> > > On Tue, Sep 20, 2005 at 08:48:33AM +0200, Sven Luther wrote:
> > > > Hello,
> > > >
> > > > I think it should be time we did a 2.6.12-7 upload, with all the fixes that
> > > > those bring in, especially the powerpc64 nvidiafb disabling one, before we do
> > > > 2.6.13-1.
> > > >
> > > > Not so sure about the 2.6.13-1 status, it should work just fine with yaird (i
> > > > am using it here now), and i was really impressed about yaird, it did detect
> > > > all my stuff from the start, including the input device, the filesystem
> > > > drivers and so on, but i guess most here are more interested in
> > > > initramfs-tools, because of the ubuntu connection maybe ?
> > > >
> > > > Anyway, i am in favour of doing a 2.6.12-7 upload tomorrow or so, so if anyone
> > > > has anything to say about this, please do so now.
> > >
> > > I have just added the relevant portions of 2.6.13.1 and 2.6.13.2
> > > to SVN, which was the main thing I have outstanding for 2.6.12-7.
> >
> > Thanks, ...
> >
> > Does that mean that 2.6.12-7 is actually releasable ? Anyone has more comment
> > on it or stuff he wants to go in ? If there is nothing of the sort, i will
> > upload those on tomorrow.
>
> Actually, I think I broke the build with those patches.
> I'm looking into it now.
>
> drivers/scsi/aacraid/aachba.c: In function 'aac_read':
> drivers/scsi/aacraid/aachba.c:869: error: 'struct aac_dev' has no member named 'max_fib_size'
> make[7]: *** [drivers/scsi/aacraid/aachba.o] Error 1
> make[6]: *** [drivers/scsi/aacraid] Error 2
> make[5]: *** [drivers/scsi] Error 2
> make[4]: *** [drivers] Error 2
I have removed the aacraid-bad-BUG_ON-fix.patch patch and the build
seems fine now. The patch resolves a problem introduced between 2.6.12
and 2.6.13 when variable FIB size support was added. See Linus' Git tree
7c00ffa314bf0fb0e23858bbebad33b48b6abbb9 for that change.
--
Horms
Reply to: