From: "Eric Bénard" <eric@eukrea.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-mtd@lists.infradead.org, dedekind1@gmail.com
Subject: Re: [PATCH] mtd: mxc_nand: do not depend on disabling the irq in the interrupt handler
Date: Fri, 15 Oct 2010 21:34:47 +0200 [thread overview]
Message-ID: <4CB8ACD7.6070206@eukrea.com> (raw)
In-Reply-To: <1285240612.29268.76.camel@localhost>
Hi David,
Le 23/09/2010 13:16, Artem Bityutskiy a écrit :
> On Tue, 2010-09-21 at 09:40 +0200, Sascha Hauer wrote:
>> This patch reverts the driver to enabling/disabling the NFC interrupt
>> mask rather than enabling/disabling the system interrupt. This cleans
>> up the driver so that it doesn't rely on interrupts being disabled
>> within the interrupt handler.
>> For i.MX21 we keep the current behaviour, that is calling
>> enable_irq/disable_irq_nosync to enable/disable interrupts.
>> This patch is based on earlier work by John Ogness.
>>
>> Signed-off-by: Sascha Hauer<s.hauer@pengutronix.de>
>> Acked-by: John Ogness<john.ogness@linutronix.de>
>> Tested-by: John Ogness<john.ogness@linutronix.de>
>
> I've created l2-mtd-2.6.git/for-2.6.36 branch, pushed your patch there,
> pinged dwmw2 for you. I do not give you any guarantees this will reach
> 2.6.36, you have to ping dwmw2.
>
Would that be possible to merge Artem's l2-mtd-2.6.git/for-2.6.36 branch for
2.6.36 (or at least cherry-pick 34e15930f2c322389d4f946bf891601a2d1e4280 from
this branch) ? Without it mxc-nand is broken in 2.6.36.
Many thanks
Eric
prev parent reply other threads:[~2010-10-15 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 7:40 [GIT PULL] mxc nand patch for -rc Sascha Hauer
2010-09-21 7:40 ` [PATCH] mtd: mxc_nand: do not depend on disabling the irq in the interrupt handler Sascha Hauer
2010-09-23 11:16 ` Artem Bityutskiy
2010-09-29 7:28 ` Sascha Hauer
2010-09-30 19:21 ` Eric Bénard
2010-10-04 6:58 ` Uwe Kleine-König
2010-10-15 19:34 ` Eric Bénard [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=4CB8ACD7.6070206@eukrea.com \
--to=eric@eukrea.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=s.hauer@pengutronix.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 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.