From: dwalker@fifo99.com (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch for 2.6.31] zaurus c3000 aka spitz: fix resume
Date: Wed, 09 Sep 2009 07:49:00 -0700 [thread overview]
Message-ID: <1252507740.14793.115.camel@desktop> (raw)
In-Reply-To: <20090909075024.GA1400@ucw.cz>
On Wed, 2009-09-09 at 09:50 +0200, Pavel Machek wrote:
> Hi, Linus!
>
> Spitz resume was broken for year or likely two, and it would be very
> nice to fix it for 2.6.31 release. One liner is below, and it really
> can not harm. It already is in Eric's fix queue, so pulling that for
> .31 should work, too.
>
> Do you think you could take it?
One checkpatch error here..
ERROR: trailing whitespace
#77: FILE: arch/arm/mach-pxa/sharpsl_pm.c:681:
+^Iif ((!sharpsl_pm.machinfo->read_devdata(SHARPSL_STATUS_LOCK)) || $
total: 1 errors, 0 warnings, 10 lines checked
Daniel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Walker <dwalker@fifo99.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: rpurdie@rpsys.net, lenz@cs.wisc.edu,
kernel list <linux-kernel@vger.kernel.org>,
Dirk@Opfer-Online.de, arminlitzel@web.de,
Cyril Hrubis <metan@ucw.cz>,
thommycheck@gmail.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
dbaryshkov@gmail.com, omegamoon@gmail.com, eric.y.miao@gmail.com,
utx@penguin.cz, Russell King <rmk@arm.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch for 2.6.31] zaurus c3000 aka spitz: fix resume
Date: Wed, 09 Sep 2009 07:49:00 -0700 [thread overview]
Message-ID: <1252507740.14793.115.camel@desktop> (raw)
In-Reply-To: <20090909075024.GA1400@ucw.cz>
On Wed, 2009-09-09 at 09:50 +0200, Pavel Machek wrote:
> Hi, Linus!
>
> Spitz resume was broken for year or likely two, and it would be very
> nice to fix it for 2.6.31 release. One liner is below, and it really
> can not harm. It already is in Eric's fix queue, so pulling that for
> .31 should work, too.
>
> Do you think you could take it?
One checkpatch error here..
ERROR: trailing whitespace
#77: FILE: arch/arm/mach-pxa/sharpsl_pm.c:681:
+^Iif ((!sharpsl_pm.machinfo->read_devdata(SHARPSL_STATUS_LOCK)) || $
total: 1 errors, 0 warnings, 10 lines checked
Daniel
next prev parent reply other threads:[~2009-09-09 14:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 7:50 [patch for 2.6.31] zaurus c3000 aka spitz: fix resume Pavel Machek
2009-09-09 7:50 ` Pavel Machek
2009-09-09 14:37 ` Eric Miao
2009-09-09 14:37 ` Eric Miao
2009-09-09 18:23 ` Russell King - ARM Linux
2009-09-09 18:23 ` Russell King - ARM Linux
2009-09-10 19:19 ` Pavel Machek
2009-09-10 19:19 ` Pavel Machek
2009-09-10 22:41 ` Russell King - ARM Linux
2009-09-10 22:41 ` Russell King - ARM Linux
2009-09-11 1:19 ` Eric Miao
2009-09-11 1:19 ` Eric Miao
2009-09-15 11:33 ` Pavel Machek
2009-09-15 11:33 ` Pavel Machek
2009-09-09 14:49 ` Daniel Walker [this message]
2009-09-09 14:49 ` Daniel Walker
2009-09-10 0:40 ` Eric Miao
2009-09-10 0:40 ` Eric Miao
2009-09-10 19:05 ` Pavel Machek
2009-09-10 19:05 ` Pavel Machek
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=1252507740.14793.115.camel@desktop \
--to=dwalker@fifo99.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 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.