All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	Bryan Evenson <bevenson@melinkcorp.com>,
	Boris BREZILLON <boris.brezillon@free-electrons.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
	"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	Andrew Victor <linux@maxim.org.za>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] rtc: rtc-at91rm9200: fix infinite wait for ACKUPD irq
Date: Wed, 7 May 2014 10:03:18 +0200	[thread overview]
Message-ID: <5369E8C6.1070409@atmel.com> (raw)
In-Reply-To: <20140506211040.GF11243@piout.net>

On 06/05/2014 23:10, Alexandre Belloni :
> Hi,
> 
> On 06/05/2014 at 19:06:56 +0000, Bryan Evenson wrote :
>>
>> I'd assume this patch would be backported to the longterm releases?
>>
> 
> If by longterm, you mean the linux4sam tree, 3.10 branch, it is up to
> Nicolas to take it. I believe it will be pretty easy to convince him ;)

Absolutely, it is always easy to convince me with:
- good commit message
- script to reproduce the issue
- follow-up of the patch plus testing
- dialogue between skilled kernel developers

So, yes, I will "ack" the patch and immediately integrate it in our
linux4sam 3.10 branch.

On the other hand, I let Boris add the "stable" tag to his original patch.

Thanks to all of you for this fix. Bye,
-- 
Nicolas Ferre

WARNING: multiple messages have this Message-ID (diff)
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] rtc: rtc-at91rm9200: fix infinite wait for ACKUPD irq
Date: Wed, 7 May 2014 10:03:18 +0200	[thread overview]
Message-ID: <5369E8C6.1070409@atmel.com> (raw)
In-Reply-To: <20140506211040.GF11243@piout.net>

On 06/05/2014 23:10, Alexandre Belloni :
> Hi,
> 
> On 06/05/2014 at 19:06:56 +0000, Bryan Evenson wrote :
>>
>> I'd assume this patch would be backported to the longterm releases?
>>
> 
> If by longterm, you mean the linux4sam tree, 3.10 branch, it is up to
> Nicolas to take it. I believe it will be pretty easy to convince him ;)

Absolutely, it is always easy to convince me with:
- good commit message
- script to reproduce the issue
- follow-up of the patch plus testing
- dialogue between skilled kernel developers

So, yes, I will "ack" the patch and immediately integrate it in our
linux4sam 3.10 branch.

On the other hand, I let Boris add the "stable" tag to his original patch.

Thanks to all of you for this fix. Bye,
-- 
Nicolas Ferre

  reply	other threads:[~2014-05-07  8:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 18:55 [BUG] at91: rtc: Uinterruptable sleep state on hwclock -w -u Bryan Evenson
2014-05-05 20:23 ` [PATCH] rtc: rtc-at91rm9200: fix lost ACKUPD interrupt Boris BREZILLON
2014-05-05 20:23   ` Boris BREZILLON
2014-05-05 20:44   ` Bryan Evenson
2014-05-05 20:44     ` Bryan Evenson
2014-05-06 11:36   ` Bryan Evenson
2014-05-06 11:36     ` Bryan Evenson
2014-05-06 12:22   ` Bryan Evenson
2014-05-06 12:22     ` Bryan Evenson
2014-05-06 14:28     ` [PATCH] rtc: rtc-at91rm9200: fix infinite wait for ACKUPD irq Boris BREZILLON
2014-05-06 14:28       ` Boris BREZILLON
2014-05-06 19:06       ` Bryan Evenson
2014-05-06 19:06         ` Bryan Evenson
2014-05-06 20:43         ` Boris BREZILLON
2014-05-06 20:43           ` Boris BREZILLON
2014-05-06 21:10         ` Alexandre Belloni
2014-05-06 21:10           ` Alexandre Belloni
2014-05-07  8:03           ` Nicolas Ferre [this message]
2014-05-07  8:03             ` Nicolas Ferre

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=5369E8C6.1070409@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=bevenson@melinkcorp.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@maxim.org.za \
    --cc=plagnioj@jcrosoft.com \
    --cc=rtc-linux@googlegroups.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 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.