From: Pavel Machek <pavel@ucw.cz>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: Stanislav Brabec <utx@penguin.cz>,
thommycheck@gmail.com, Russell King <rmk@arm.linux.org.uk>,
dbaryshkov@gmail.com, Cyril Hrubis <metan@ucw.cz>,
arminlitzel@web.de, kernel list <linux-kernel@vger.kernel.org>,
Dirk@opfer-online.de, lenz@cs.wisc.edu, rpurdie@rpsys.net,
omegamoon@gmail.com, eric.miao@marvell.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: zaurus c3000 aka spitz: fix resume
Date: Tue, 8 Sep 2009 00:32:08 +0200 [thread overview]
Message-ID: <20090907223208.GC695@elf.ucw.cz> (raw)
In-Reply-To: <f17812d70909070908l26541562iec36a117c155aa08@mail.gmail.com>
On Tue 2009-09-08 00:08:13, Eric Miao wrote:
> On Sun, Sep 6, 2009 at 9:32 PM, Stanislav Brabec<utx@penguin.cz> wrote:
> > Pavel Machek wrote:
> >> sharpsl_pm.c code tries to read battery state very early during
> >> resume, but those battery meters are connected on SPI and that's only
> >> resumed way later.
> >>
> >> Replace the check with simple checking of battery fatal signal, that
> >> actually works at this stage.
> >
> > Tested on:
>
> Applied to 'fix'.
Thanks. Is there still chance to push it to 2.6.31? That would help a
lot. Alternatively, we could push it to the -stable tree at least...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-09-07 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 5:28 zaurus c3000 aka spitz: fix resume Pavel Machek
2009-09-06 13:32 ` Stanislav Brabec
2009-09-07 11:39 ` Pavel Machek
2009-09-07 16:08 ` Eric Miao
2009-09-07 22:32 ` Pavel Machek [this message]
2009-09-06 18:04 ` Dmitry Eremin-Solenikov
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=20090907223208.GC695@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Dirk@opfer-online.de \
--cc=arminlitzel@web.de \
--cc=dbaryshkov@gmail.com \
--cc=eric.miao@marvell.com \
--cc=eric.y.miao@gmail.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=rmk@arm.linux.org.uk \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--cc=utx@penguin.cz \
/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