From: Tony Lindgren <tony@atomide.com>
To: Michael Opdenacker <michael.opdenacker@linaro.org>
Cc: linux@arm.linux.org.uk, khilman@ti.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, patches@linaro.org
Subject: Re: [PATCH 1/1] arm: omap: removed obsolete IRQF_DISABLED
Date: Thu, 3 Nov 2011 15:15:01 -0700 [thread overview]
Message-ID: <20111103221501.GD31337@atomide.com> (raw)
In-Reply-To: <1318139198-6865-2-git-send-email-michael.opdenacker@linaro.org>
* Michael Opdenacker <michael.opdenacker@linaro.org> [111008 22:13]:
> This flag is a NOOP since 2.6.36
Looks like there's an ARM wide patch to do this with
"[PATCH 03/55] arm: irq: Remove IRQF_DISABLED".
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] arm: omap: removed obsolete IRQF_DISABLED
Date: Thu, 3 Nov 2011 15:15:01 -0700 [thread overview]
Message-ID: <20111103221501.GD31337@atomide.com> (raw)
In-Reply-To: <1318139198-6865-2-git-send-email-michael.opdenacker@linaro.org>
* Michael Opdenacker <michael.opdenacker@linaro.org> [111008 22:13]:
> This flag is a NOOP since 2.6.36
Looks like there's an ARM wide patch to do this with
"[PATCH 03/55] arm: irq: Remove IRQF_DISABLED".
Regards,
Tony
next prev parent reply other threads:[~2011-11-03 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 5:46 [PATCH 0/1] arm: omap: remove obsolete IRQF_DISABLED Michael Opdenacker
2011-10-09 5:46 ` Michael Opdenacker
2011-10-09 5:46 ` [PATCH 1/1] arm: omap: removed " Michael Opdenacker
2011-10-09 5:46 ` Michael Opdenacker
2011-11-03 22:15 ` Tony Lindgren [this message]
2011-11-03 22:15 ` Tony Lindgren
2011-11-04 14:10 ` Michael Opdenacker
2011-11-04 14:10 ` 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=20111103221501.GD31337@atomide.com \
--to=tony@atomide.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=michael.opdenacker@linaro.org \
--cc=patches@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.