Re: RFC: PCI quirks update for 2.6.16

[Adrian Bunk <bunk@stusta.de>]

On Mon, Dec 11, 2006 at 12:48:10PM +0000, Sergio Monteiro Basto wrote:
> On Mon, 2006-12-11 at 13:41 +0100, Adrian Bunk wrote:
> > On Mon, Dec 11, 2006 at 01:42:48AM +0000, Sergio Monteiro Basto wrote:
> > > On Sun, 2006-12-10 at 17:00 +0100, Adrian Bunk wrote:
> > > > +DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID,
> > > > quirk_via_irq);
> > > 
> > > This is back to state of kernel 2.6.16 final (without .x)
> > > 
> > > In kernel 2.6.17 final we got
> > > (http://lkml.org/lkml/2006/4/19/16)
> > > commit 75cf7456dd87335f574dcd53c4ae616a2ad71a11 
> > > Author: Chris Wedgwood <cw@f00f.org>
> > > Date:   Tue Apr 18 23:57:09 2006 -0700 
> > >     Signed-off-by: Chris Wedgwood <cw@f00f.org>
> > >     Acked-by: Jeff Garzik <jeff@garzik.org>
> > >     Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> > > and 
> > > commit a7b862f663d81858531dfccc0537bc9d8a2a4121
> > > Author: Chris Wedgwood <cw@f00f.org>
> > > Date:   Mon May 15 09:43:55 2006 -0700
> > >     [PATCH] VIA quirk fixup, additional PCI IDs    
> > > 
> > > BUT the latest stable and tested patch is the commit 09d6029f43ebbe7307854abdae204c25d711ff94
> > > PCI: VIA IRQ quirk behaviour change, which in my opinion that should go in.
> > 
> > Commit 09d6029f43ebbe7307854abdae204c25d711ff94 is what Alan wasn't 
> > happy with, and -mm contains Alan's solution...
> 
> No, Alan's solution was a post solution , which still on -mm, I think .

Look at the patch in -mm, it contains essentially the next rewrite of 
this quirk...

> Thanks,

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

-
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/