Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: alex@digriz.org.uk (Alexander Clouter)
To: linux-arm-kernel@lists.infradead.org
Subject: arm / kirkwood (openrd): cpu_idle
Date: Fri, 16 Oct 2009 12:50:57 +0100	[thread overview]
Message-ID: <1a3mq6-ga5.ln1@chipmunk.wormnet.eu> (raw)
In-Reply-To: ad9478410910150556h346c1042l48589843087e6fba@mail.gmail.com

Joel Stanley <joel@jms.id.au> wrote:
>
> On Thu, Oct 15, 2009 at 22:58, Dieter Kiermaier <dk-arm-linux@gmx.de> wrote:
>>
>> Am Donnerstag 15 Oktober 2009 14:10:22 schrieb Sascha Silbe:
>
>>> On Thu, Oct 15, 2009 at 01:52:41PM +0200, Dieter Kiermaier wrote:
>>>
>>> > But it looks like that in rc4 something has changed so the patch
>>> > didn't apply without errors.
>>> It was quite easy to resolve (even though I don't understand any of the
>>> touched code), see [1] for a rebased patch.
> 
> I can confirm that the patch fixes the issue; I have been testing for
> 48 hours on an openrd-client without seeing the WARNING.
> 
>>> I'm wondering why it wasn't merged upstream yet, though.
>>
>> I'm wondering, too.
> 
> Agreed.  What can we do to help it on it's way?
> 
I guess someone could add a bunch of Tested-By's to the LKML posting.

http://patchwork.kernel.org/patch/50728/

Cheers

-- 
Alexander Clouter
.sigmonster says: "We live, in a very kooky time."
                  		-- Herb Blashtfalt

  reply	other threads:[~2009-10-16 11:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15 11:52 arm / kirkwood (openrd): cpu_idle Dieter Kiermaier
2009-10-15 12:10 ` Sascha Silbe
2009-10-15 12:28   ` Dieter Kiermaier
2009-10-15 12:56     ` Joel Stanley
2009-10-16 11:50       ` Alexander Clouter [this message]
2009-10-17 15:49         ` Martin Michlmayr

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=1a3mq6-ga5.ln1@chipmunk.wormnet.eu \
    --to=alex@digriz.org.uk \
    --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