From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
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.arm.linux.org.uk>,
dbaryshkov@gmail.com, omegamoon@gmail.com, eric.miao@marvell.com,
utx@penguin.cz
Subject: Re: Zaurus suspend saga
Date: Mon, 7 Sep 2009 12:04:41 +0200 [thread overview]
Message-ID: <20090907100441.GF23450@elf.ucw.cz> (raw)
In-Reply-To: <200909061903.10542.rjw@sisk.pl>
On Sun 2009-09-06 19:03:10, Rafael J. Wysocki wrote:
> On Sunday 06 September 2009, Pavel Machek wrote:
> > Hi!
> >
> > Even with mtd regression fixed, spitz will still not suspend/resume
> > correctly.
>
> Is the regression fixed in the Linus' tree, or do you still need to apply the
> revert patch?
mtd regression is fixed.
battery vs. SPI regression is very very very old, and seems to be
fixed by the one-liner.
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 10:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 5:26 Zaurus suspend saga Pavel Machek
2009-09-06 17:03 ` Rafael J. Wysocki
2009-09-06 18:01 ` Stanislav Brabec
2009-09-07 10:04 ` Pavel Machek [this message]
2009-09-06 22:29 ` Richard Purdie
2009-09-07 1:06 ` Eric Miao
2009-09-07 11:03 ` Pavel Machek
2009-09-07 11:34 ` Stanislav Brabec
2009-09-07 11:48 ` Russell King - ARM Linux
2009-09-16 12:25 ` Stanislav Brabec
2009-10-02 4:13 ` Pavel Machek
2009-10-02 7:36 ` Joe Perches
2009-09-07 12:05 ` Dmitry Eremin-Solenikov
2009-09-07 11:31 ` Pavel Machek
2009-09-07 13:10 ` Stanislav Brabec
2009-09-07 14:07 ` Richard Purdie
2009-09-07 14:52 ` Eric Miao
2009-09-07 20:36 ` Dmitry Eremin-Solenikov
2009-09-07 14:46 ` Eric Miao
2009-09-08 21:19 ` Pavel Machek
2009-09-08 21:53 ` Pavel Machek
2009-09-09 9:28 ` Stanislav Brabec
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=20090907100441.GF23450@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=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=rjw@sisk.pl \
--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