From: Olaf Dabrunz <od@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stefan Assmann <sassmann@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Jon Masters <jonathan@jonmasters.org>, Olaf Dabrunz <od@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
Ihno Krumreich <ihno@suse.de>, Sven Dietrich <sdietrich@suse.de>,
Daniel Gollub <dgollub@suse.de>,
Felix Foerster <ffoerster@suse.de>
Subject: Re: [PATCH 0/5] Boot IRQ quirks and rerouting [repost]
Date: Wed, 18 Jun 2008 15:22:01 +0200 [thread overview]
Message-ID: <20080618132201.GH10105@suse.de> (raw)
In-Reply-To: <20080618115819.GA13714@elte.hu>
On 18-Jun-08, Ingo Molnar wrote:
>
> * Stefan Assmann <sassmann@suse.de> wrote:
>
> > These patches are against linux-2.6-tip, auto-x86-next.
> >
> > The AMD/ATI and Broadcomm patches are not included yet, we're working
> > on getting things ready for submission.
> >
> > The patch for the bootirqquirk= parameter will be released later.
>
> applied, thanks Stefan. I have created a new
Cool. :)
> tip/x86/pci-ioapic-boot-irq-quirks topic branch for this. Lets see how
> these changes work out in practice.
Thanks for creating the branch.
--
Olaf Dabrunz (od/odabrunz), SUSE Linux Products GmbH, Nürnberg
prev parent reply other threads:[~2008-06-18 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 14:35 [PATCH 0/5] Boot IRQ quirks and rerouting [repost] Stefan Assmann
2008-06-11 14:35 ` [PATCH 1/5] Add PCI IDs for devices that need boot irq quirks Stefan Assmann
2008-06-11 14:35 ` [PATCH 2/5] Introduce pci=noioapicquirk kernel cmdline option Stefan Assmann
2008-06-11 14:35 ` [PATCH 3/5] Introduce pci=ioapicreroute " Stefan Assmann
2008-06-11 14:35 ` [PATCH 4/5] Add quirk to disable boot interrupt generation on intel 6300ESB Stefan Assmann
2008-06-11 14:35 ` [PATCH 5/5] reroute PCI interrupt to legacy boot interrupt equivalent Stefan Assmann
2008-06-18 11:58 ` [PATCH 0/5] Boot IRQ quirks and rerouting [repost] Ingo Molnar
2008-06-18 12:52 ` Ingo Molnar
2008-06-18 13:22 ` Olaf Dabrunz [this message]
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=20080618132201.GH10105@suse.de \
--to=od@suse.de \
--cc=dgollub@suse.de \
--cc=ffoerster@suse.de \
--cc=hpa@zytor.com \
--cc=ihno@suse.de \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sassmann@suse.de \
--cc=sdietrich@suse.de \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).