From: Ian Campbell <Ian.Campbell@citrix.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>
Subject: Re: [PATCH] xen: Use new irq_move functions
Date: Fri, 25 Mar 2011 10:04:02 +0000 [thread overview]
Message-ID: <1301047442.11560.194.camel@cthulhu.hellion.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1103242135380.31464@localhost6.localdomain6>
On Thu, 2011-03-24 at 20:37 +0000, Thomas Gleixner wrote:
> These functions take irq_data as an argument and avoid a redundant
> lookup in the sparse irq case.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Looks good to me.
Acked-by: Ian Campbell <ian.campbell@citrix.com>
Do you want to carry this in your tree or shall we pick it up? (not sure
if this is part of a wider treewide series or not)
> Cc: Jeremy Fitzhardinge <jeremy@goop.org>
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> ---
> drivers/xen/events.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> Index: linux-2.6-tip/drivers/xen/events.c
> ===================================================================
> --- linux-2.6-tip.orig/drivers/xen/events.c
> +++ linux-2.6-tip/drivers/xen/events.c
> @@ -585,7 +585,7 @@ static void ack_pirq(struct irq_data *da
> {
> int evtchn = evtchn_from_irq(data->irq);
>
> - move_native_irq(data->irq);
> + irq_move_irq(data);
>
> if (VALID_EVTCHN(evtchn)) {
> mask_evtchn(evtchn);
> @@ -1339,7 +1339,7 @@ static void ack_dynirq(struct irq_data *
> {
> int evtchn = evtchn_from_irq(data->irq);
>
> - move_masked_irq(data->irq);
> + irq_move_masked_irq(data);
>
> if (VALID_EVTCHN(evtchn))
> unmask_evtchn(evtchn);
next prev parent reply other threads:[~2011-03-25 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 20:37 Thomas Gleixner
2011-03-25 10:04 ` Ian Campbell [this message]
2011-03-25 11:54 ` Thomas Gleixner
2011-03-25 12:23 ` Konrad Rzeszutek Wilk
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=1301047442.11560.194.camel@cthulhu.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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®