public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Iyer, Sundar" <sundar.iyer@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lethal@linux-sh.org" <lethal@linux-sh.org>,
	"arjan@linux.intel.com" <arjan@linux.intel.com>,
	"Monroy, German" <german.monroy@intel.com>
Subject: RE: [PATCH v2] x86/irq: handle chained interrupts during IRQ migration
Date: Wed, 6 Jun 2012 23:01:59 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1206062301330.3086@ionos> (raw)
In-Reply-To: <2FABAEF0D3DCAF4F9C9628D6E2F968451D8329@BGSMSX102.gar.corp.intel.com>

On Wed, 6 Jun 2012, Iyer, Sundar wrote:
> 
> Any comments on this version? Or do you suggest to add a new flag in
> the accessors and set it?

That's what I said IIRC.

      reply	other threads:[~2012-06-06 21:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30  9:28 [PATCH v2] x86/irq: handle chained interrupts during IRQ migration Sundar Iyer
2012-06-06 17:52 ` Iyer, Sundar
2012-06-06 21:01   ` 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.1206062301330.3086@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