From: Thomas Gleixner <tglx@linutronix.de>
To: "Iyer, Sundar" <sundar.iyer@intel.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"arjan@linux.intel.com" <arjan@linux.intel.com>,
"Monroy, German" <german.monroy@intel.com>
Subject: RE: [PATCH v3 1/1] x86/irq: handle chained interrupts during IRQ migration
Date: Mon, 2 Jul 2012 11:02:39 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1207021101460.2793@ionos> (raw)
In-Reply-To: <2FABAEF0D3DCAF4F9C9628D6E2F9684521253F@BGSMSX102.gar.corp.intel.com>
On Mon, 2 Jul 2012, Iyer, Sundar wrote:
> Hi Thomas/Paul,
>
> Any comments on the latest patch set?
Yes, it does neither apply on Linus tree nor on tip/irq/core branch.
Thanks,
tglx
prev parent reply other threads:[~2012-07-02 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 3:55 [PATCH v3 1/1] x86/irq: handle chained interrupts during IRQ migration Sundar Iyer
2012-06-25 5:31 ` Paul Mundt
2012-07-02 4:22 ` Iyer, Sundar
2012-07-02 9:02 ` Thomas Gleixner [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=alpine.LFD.2.02.1207021101460.2793@ionos \
--to=tglx@linutronix.de \
--cc=arjan@linux.intel.com \
--cc=german.monroy@intel.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sundar.iyer@intel.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