From: yong.zhang0@gmail.com (Yong Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 53/57] sound: irq: Remove IRQF_DISABLED
Date: Wed, 21 Sep 2011 20:12:41 +0800 [thread overview]
Message-ID: <20110921121241.GC2550@zhy> (raw)
In-Reply-To: <alpine.LFD.2.02.1109211154280.2723@ionos>
On Wed, Sep 21, 2011 at 11:55:36AM +0200, Thomas Gleixner wrote:
> On Wed, 21 Sep 2011, Takashi Iwai wrote:
>
> > At Wed, 21 Sep 2011 17:28:54 +0800,
> > Yong Zhang wrote:
> > >
> > > Since commit [c58543c8: genirq: Run irq handlers with interrupts disabled],
> >
> > Hm, this id hits a different commit:
> > commit c58543c869606532c2382f027d6466f4672ea756
> > Author: David S. Miller <davem@davemloft.net>
> > Date: Tue Oct 13 00:49:09 2009 -0700
> >
> > sparc64: Set IRQF_DISABLED on LDC channel IRQs.
> >
> > You mean commit e58aa3d2d0cc01ad8d6f7f640a0670433f794922?
>
> Yeah.
>
> > > We run all interrupt handlers with interrupts disabled
> > > and we even check and yell when an interrupt handler
> > > returns with interrupts enabled (see commit [b738a50a:
> > > genirq: Warn when handler enables interrupts]).
> > >
> > > So now this flag is a NOOP and can be removed.
> > >
> > > Signed-off-by: Yong Zhang <yong.zhang0@gmail.com>
> > > Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> >
> > Do you want to merge by yourself or shall I take it to sound git tree?
> > Since IRQF_DISABLED isn't used, it can be applied safely in 3.1-based
> > tree, right?
>
> Yes, please go ahead. I'll pick up the leftovers.
Takashi, if you take it, could you please modify that commit id to the
right one?
Otherwise I could change it when I refresh this patchset.
Thanks,
Yong
next prev parent reply other threads:[~2011-09-21 12:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1316597339-29861-1-git-send-email-yong.zhang0@gmail.com>
2011-09-21 9:28 ` [PATCH 24/57] SCSI: irq: Remove IRQF_DISABLED Yong Zhang
2011-09-21 9:28 ` [PATCH 30/57] dmaengine: " Yong Zhang
2011-09-21 9:28 ` [PATCH 32/57] i2c: " Yong Zhang
2011-09-21 9:28 ` [PATCH 46/57] rtc: " Yong Zhang
2011-09-21 9:52 ` Wan ZongShun
2011-09-21 10:31 ` [rtc-linux] " Wolfram Sang
2011-09-21 9:28 ` [PATCH 49/57] video: " Yong Zhang
2011-09-21 20:22 ` David Brown
2011-09-21 9:28 ` [PATCH 51/57] watchdog: " Yong Zhang
2011-09-21 9:28 ` [PATCH 53/57] sound: " Yong Zhang
2011-09-21 9:52 ` Takashi Iwai
2011-09-21 9:55 ` Thomas Gleixner
2011-09-21 12:12 ` Yong Zhang [this message]
2011-09-22 9:42 ` Takashi Iwai
2011-09-21 12:10 ` Yong Zhang
2011-09-21 10:21 ` Ujfalusi, Peter
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=20110921121241.GC2550@zhy \
--to=yong.zhang0@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).