From: Ingo Molnar <mingo@elte.hu>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: sedat.dilek@gmail.com, Florian Mickler <florian@mickler.org>,
Paul Bolle <pebolle@tiscali.nl>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
kurup_avinash@yahoo.com, maciej.rutecki@gmail.com, rjw@sisk.pl,
zersaa@gmail.com, stable@kernel.org
Subject: Re: [PATCH][POKE] Skip looking for ioapic overrides when ioapics are not present
Date: Sat, 2 Apr 2011 20:43:14 +0200 [thread overview]
Message-ID: <20110402184314.GA17191@elte.hu> (raw)
In-Reply-To: <m1vcyxeavf.fsf@fess.ebiederm.org>
* Eric W. Biederman <ebiederm@xmission.com> wrote:
> Ingo Molnar <mingo@elte.hu> writes:
>
> > * Eric W. Biederman <ebiederm@xmission.com> wrote:
> >
> >> I don't have a clue why my patch got lost, [...]
> >
> > It was not lost, it broke the build. You were notified but never followed up
> > with a working patch:
> >
> > https://lkml.org/lkml/2010/10/2/91
> >
> > and a different patch was applied to get rid of the warning messages. We can
> > apply your patch (and that patch can undo the other fix), but it has to build,
> > obviously.
>
> Ingo any clue why I this message didn't make it to me directly but I
> only received it through the linux-kernel?
Hm, no idea - i did not receive any email bounce message.
Did you get this one directly?
Thanks,
Ingo
next prev parent reply other threads:[~2011-04-02 18:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 8:01 [PATCH][POKE] Skip looking for ioapic overrides when ioapics are not present Florian Mickler
2011-03-31 8:43 ` Ingo Molnar
2011-03-31 10:59 ` Florian Mickler
2011-04-02 15:11 ` [stable] " Andi Kleen
2011-04-02 18:35 ` Ingo Molnar
2011-04-01 1:23 ` [PATCH v2] x86, ioapic: " Florian Mickler
2011-04-01 6:20 ` Ingo Molnar
2011-04-01 6:43 ` Eric W. Biederman
2011-04-01 6:47 ` Len Brown
2011-04-01 7:50 ` Ingo Molnar
2011-04-01 15:44 ` [PATCH] x86, ioapic: move acpi_get_override_irq to acpi.c Florian Mickler
2011-04-01 16:26 ` Florian Mickler
2011-04-03 14:34 ` Florian Mickler
2011-04-04 15:00 ` Ingo Molnar
2011-04-12 7:39 ` Ingo Molnar
2011-04-12 19:53 ` Florian Mickler
2011-04-12 20:01 ` [PATCH 1/2 v2] x86, ioapic: Skip looking for ioapic overrides when ioapics are not present Florian Mickler
2011-04-12 20:01 ` [PATCH 2/2 v2] x86, ioapic: move acpi_get_override_irq to acpi.c Florian Mickler
2011-04-15 10:19 ` Ingo Molnar
2011-05-17 14:38 ` Florian Mickler
2011-03-31 8:48 ` [PATCH][POKE] Skip looking for ioapic overrides when ioapics are not present Paul Bolle
2011-03-31 10:53 ` Florian Mickler
2011-03-31 11:01 ` Sedat Dilek
2011-03-31 12:05 ` Eric W. Biederman
2011-03-31 12:43 ` Ingo Molnar
2011-04-02 0:48 ` Eric W. Biederman
2011-04-02 18:43 ` Ingo Molnar [this message]
2011-04-02 22:21 ` Eric W. Biederman
2011-03-31 13:16 ` Florian Mickler
2011-03-31 13:25 ` Sedat Dilek
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=20110402184314.GA17191@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=florian@mickler.org \
--cc=kurup_avinash@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=pebolle@tiscali.nl \
--cc=rjw@sisk.pl \
--cc=sedat.dilek@gmail.com \
--cc=stable@kernel.org \
--cc=zersaa@gmail.com \
/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).