[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080715093527.GB2297@suse.de>
Date: Tue, 15 Jul 2008 11:35:28 +0200
From: Olaf Dabrunz <od@...e.de>
To: Ingo Molnar <mingo@...e.hu>
Cc: Jesse Barnes <jbarnes@...tuousgeek.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Jon Masters <jonathan@...masters.org>,
Stefan Assmann <sassmann@...e.de>,
LKML <linux-kernel@...r.kernel.org>,
Ihno Krumreich <ihno@...e.de>,
Sven Dietrich <sdietrich@...e.de>,
Daniel Gollub <dgollub@...e.de>,
Felix Foerster <ffoerster@...e.de>
Subject: Re: [PATCH 0/3] Boot IRQ quirks for Broadcom and AMD/ATI
On 14-Jul-08, Ingo Molnar wrote:
>
> * Olaf Dabrunz <od@...e.de> wrote:
>
> > On 14-Jul-08, Olaf Dabrunz wrote:
> > > I am working on a consolidated patch set for AKMP. It integrates all
> > > fixes and adds a config option CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS
> > > (prepared by Stefan Assmann), which can default to off for vanilla and to
> > > on for RT / threaded IRQ handling. This means that the whole patchset
> > > can (in principle) be applied to vanilla and RT without change. Also
> > > CONFIG_PREEMPT_HARDIRQ can "select CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS".
> > >
> > > If you don't mind, I will send the full set out today.
> >
> > On second thought and after talking to Stefan, as you think the
> > patches can go into 2.6.27 as they are, there is not much benefit in
> > integrating the fixes and the config option patch. Stefan will commit
> > the config option patch to tip tomorrow.
>
> please do not rebase the patchset, that causes us lose the testing
> status, we lose the sha1's of the commits, etc. Lets keep what we have
> in tip/x86/pci-ioapic-boot-irq-quirks and do append-only fixlets to it.
Right.
Thanks,
--
Olaf Dabrunz (od/odabrunz), SUSE Linux Products GmbH, Nürnberg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists