From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yinghai Lu <yhlu.kernel@gmail.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [patch 1/5] x2apic: fix reserved APIC register accesses in print_local_APIC()
Date: Thu, 4 Sep 2008 10:51:40 -0700 [thread overview]
Message-ID: <20080904175139.GN14481@linux-os.sc.intel.com> (raw)
In-Reply-To: <20080904110631.GC8668@elte.hu>
On Thu, Sep 04, 2008 at 04:06:31AM -0700, Ingo Molnar wrote:
>
> applied the following patches tip/irq/sparseirq:
Ingo, Shouldn't this go to tip/x86/x2apic ? Thanks.
> 0f48966: dmar: fix dmar_parse_dev() devices_cnt error condition check
> 2283240: dmar: use list_for_each_entry_safe() in dmar_dev_scope_init()
> 3f1fdb3: dmar: initialize the return value in dmar_parse_dev()
> f12c73e: dmar: fix using early fixmap mapping for DMAR table parsing
> 2c72d93: x2apic: fix reserved APIC register accesses in print_local_APIC()
>
> thanks Suresh!
>
> Ingo
next prev parent reply other threads:[~2008-09-04 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 23:58 [patch 1/5] x2apic: fix reserved APIC register accesses in print_local_APIC() Suresh Siddha
2008-09-03 23:58 ` [patch 2/5] dmar: fix using early fixmap mapping for DMAR table parsing Suresh Siddha
2008-09-03 23:58 ` [patch 3/5] dmar: initialize the return value in dmar_parse_dev() Suresh Siddha
2008-09-03 23:58 ` [patch 4/5] dmar: use list_for_each_entry_safe() in dmar_dev_scope_init() Suresh Siddha
2008-09-03 23:58 ` [patch 5/5] dmar: fix dmar_parse_dev() devices_cnt error condition check Suresh Siddha
2008-09-04 11:06 ` [patch 1/5] x2apic: fix reserved APIC register accesses in print_local_APIC() Ingo Molnar
2008-09-04 17:51 ` Suresh Siddha [this message]
2008-09-05 8:10 ` Ingo Molnar
2008-09-05 9:18 ` Jesse Barnes
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=20080904175139.GN14481@linux-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.