From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] rtc: at91rm9200: double locking bug in at91_rtc_interrupt()
Date: Tue, 17 Mar 2015 15:39:19 +0000 [thread overview]
Message-ID: <55084AA7.3020007@atmel.com> (raw)
In-Reply-To: <20150315104837.GC20691@mwanda>
Le 15/03/2015 12:01, Boris Brezillon a écrit :
> Hi Dan,
>
> On Sun, 15 Mar 2015 13:48:37 +0300
> Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
>> There is a typo here so we deadlock.
>>
>> Fixes: dd1f1f391dd7 ('rtc: at91rm9200: rework wakeup and interrupt handling')
>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>
> Thanks for fixing this bug.
>
> Alessandro, Nicolas, could you agree on who is taking this fix for
> the next -rc cycle ?
I've just collected the tags and asked to Andrew if he can take it.
Thanks for the fix and the "heads up"!
Bye,
--
Nicolas Ferre
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-03-17 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 10:48 [patch] rtc: at91rm9200: double locking bug in at91_rtc_interrupt() Dan Carpenter
2015-03-15 11:01 ` Boris Brezillon
2015-03-17 15:38 ` [PATCH] " Nicolas Ferre
2015-03-17 15:38 ` Nicolas Ferre
2015-03-17 15:38 ` Nicolas Ferre
2015-03-17 17:32 ` Dan Carpenter
2015-03-17 17:32 ` Dan Carpenter
2015-03-17 17:32 ` Dan Carpenter
2015-03-18 0:56 ` Rafael J. Wysocki
2015-03-18 1:20 ` Rafael J. Wysocki
2015-03-18 1:20 ` Rafael J. Wysocki
2015-03-17 15:39 ` Nicolas Ferre [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=55084AA7.3020007@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=kernel-janitors@vger.kernel.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.