public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: mingo@redhat.com, konrad.wilk@oracle.com, x86@kernel.org,
	tglx@linutronix.de, xen-devel@lists.xenproject.org,
	david.vrabel@citrix.com, linux-kernel@vger.kernel.org,
	hpa@zytor.com
Subject: Re: [PATCH] x86/xen: remove deprecated IRQF_DISABLED
Date: Mon, 09 Sep 2013 05:15:53 +0200	[thread overview]
Message-ID: <522D3D69.5000004@free-electrons.com> (raw)
In-Reply-To: <3b488375-6998-4681-b105-e4c6d12ceca2@default>

Hi Boris,

Thanks for your review!

On 09/08/2013 05:14 PM, Boris Ostrovsky wrote:
> ----- michael.opdenacker@free-electrons.com wrote:
>
>> This patch proposes to remove the IRQF_DISABLED flag from x86/xen
>> code. It's a NOOP since 2.6.35 and it will be removed one day.
>>
>> Signed-off-by: Michael Opdenacker
>> <michael.opdenacker@free-electrons.com>
>> ---
>>  arch/x86/xen/smp.c      | 10 +++++-----
>>  arch/x86/xen/spinlock.c |  2 +-
>>  arch/x86/xen/time.c     |  3 +--
>>  3 files changed, 7 insertions(+), 8 deletions(-)
>
> If you are cleaning up Xen's use of IRQF_DISABLED then you should
> probably also update drivers/xen/evtchn.c and drivers/xen/platform-pci.c
This definitely makes sense to do this at the same time. I've just
submitted a separate patch for this.

Thanks again,

Michael.

-- 
Michael Opdenacker, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
+33 484 258 098


  reply	other threads:[~2013-09-09  3:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-08 15:14 [PATCH] x86/xen: remove deprecated IRQF_DISABLED Boris Ostrovsky
2013-09-09  3:15 ` Michael Opdenacker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-09-07  6:46 Michael Opdenacker

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=522D3D69.5000004@free-electrons.com \
    --to=michael.opdenacker@free-electrons.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=hpa@zytor.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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