From: "Lu, Guanqun" <guanqun.lu@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>, "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"jeremy@goop.org" <jeremy@goop.org>
Subject: RE: [PATCH 1/3] add flag IRQF_NO_SUSPEND in 'struct irqaction'
Date: Mon, 20 Jul 2009 10:55:28 +0800 [thread overview]
Message-ID: <8FED46E8A9CA574792FC7AACAC38FE7701E6F48AF7@PDSMSX501.ccr.corp.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0907171615530.11571@localhost.localdomain>
>-----Original Message-----
>From: Thomas Gleixner [mailto:tglx@linutronix.de]
>Sent: Friday, July 17, 2009 10:18 PM
>To: Rafael J. Wysocki
>Cc: Lu, Guanqun; linux-kernel@vger.kernel.org; mingo@elte.hu; jeremy@goop.org
>Subject: Re: [PATCH 1/3] add flag IRQF_NO_SUSPEND in 'struct irqaction'
>
>On Fri, 17 Jul 2009, Rafael J. Wysocki wrote:
>
>> On Friday 17 July 2009, Guanqun Lu wrote:
>> > We currently only bypass IRQF_TIMER in '__disable_irq',
>> > but Xen specific IRQs should not be disabled either.
>> > This commit adds a new flag to accompolish this goal
>> > without being mixed up with IRQF_TIMER flag.
>>
>> For some obscure reasons [2/3] didn't reach my inbox. The other 2 patches
>> look fine to me.
>
>I do not receive the patches at all. Can you please resend and cc me ?
Resent now, let me know it doesn't get to your inbox again.
Guanqun
>
>Thanks,
>
> tglx
prev parent reply other threads:[~2009-07-20 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1247834204-3084-1-git-send-email-guanqun.lu@intel.com>
2009-07-17 1:52 ` Rafael J. Wysocki
2009-07-17 2:16 ` Lu, Guanqun
2009-07-17 2:41 ` Rafael J. Wysocki
2009-07-17 14:17 ` Thomas Gleixner
2009-07-20 2:55 ` Lu, Guanqun [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=8FED46E8A9CA574792FC7AACAC38FE7701E6F48AF7@PDSMSX501.ccr.corp.intel.com \
--to=guanqun.lu@intel.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--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
all inboxes | Powered by JetHome®