From: Sekhar Nori <nsekhar@ti.com>
To: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Cc: <khilman@deeprootsystems.com>, <linux@arm.linux.org.uk>,
<linux-arm-kernel@lists.infradead.org>,
<davinci-linux-open-source@linux.davincidsp.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: davinci: remove deprecated IRQF_DISABLED
Date: Thu, 12 Sep 2013 15:41:52 +0530 [thread overview]
Message-ID: <52319368.7010501@ti.com> (raw)
In-Reply-To: <1378537633-7232-1-git-send-email-michael.opdenacker@free-electrons.com>
On Saturday 07 September 2013 12:37 PM, Michael Opdenacker wrote:
> This patch proposes to remove the IRQF_DISABLED flag from Davinci code ;)
> It's a NOOP since 2.6.35, and will be removed one day
>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Thanks for the patch. Queuing for v3.13
~Sekhar
prev parent reply other threads:[~2013-09-12 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 7:07 [PATCH] ARM: davinci: remove deprecated IRQF_DISABLED Michael Opdenacker
2013-09-12 10:11 ` Sekhar Nori [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=52319368.7010501@ti.com \
--to=nsekhar@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=michael.opdenacker@free-electrons.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