From: Pavel Machek <pavel@ucw.cz>
To: Cyril Hrubis <metan@ucw.cz>
Cc: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
thommycheck@gmail.com, Marek Vasut <marek.vasut@gmail.com>,
Russell King <rmk@arm.linux.org.uk>,
arminlitzel@web.de, kernel list <linux-kernel@vger.kernel.org>,
utx@penguin.cz, lenz@cs.wisc.edu, rpurdie@rpsys.net,
omegamoon@gmail.com, eric.y.miao@gmail.com,
Linus Torvalds <torvalds@linux-foundation.org>,
zaurus-devel@www.linuxtogo.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: zaurus patches -- arm/pxa -- is Eric alive
Date: Sun, 28 Aug 2011 11:35:26 +0200 [thread overview]
Message-ID: <20110828093526.GA17995@elf.ucw.cz> (raw)
In-Reply-To: <20110711140303.GA32532@atrey.karlin.mff.cuni.cz>
Hi!
> > > There are some rather critical patches for zaurus C-3000 (spitz)
> > > available... with no response. What is going on?
> >
> > Eric seems alive. At least he've sent pull requests few days ago.
> > Maybe you can point to those patches, that you mention as critical?
>
> Perhaps the most critical one is:
>
> [PATCH] MAX1111: Fix race condition causing NULL pointer exception
>
> http://ns1.yosemitephotos.net/lists/arm-kernel/msg125356.html
> Which fixes memory corruption that caused random oops.
This one is in 3.1-rc3. Good.
> And then there is a bunch of fixes for charging and power management from
> Pavel Machek:
>
> Disable CF during suspend
>
> https://lkml.org/lkml/2011/5/21/46
This one is not. Could we get it pushed?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2011-08-28 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 13:41 Pavel Machek
2011-07-11 13:44 ` Dmitry Eremin-Solenikov
2011-07-11 14:03 ` Cyril Hrubis
2011-07-11 14:17 ` Wolfram Sang
2011-07-11 14:22 ` Cyril Hrubis
2011-07-11 18:58 ` Pavel Herrmann
2011-07-11 15:13 ` Eric Miao
2011-07-11 21:09 ` Pavel Machek
2011-08-28 9:35 ` Pavel Machek [this message]
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=20110828093526.GA17995@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=arminlitzel@web.de \
--cc=dbaryshkov@gmail.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=marek.vasut@gmail.com \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=rmk@arm.linux.org.uk \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=utx@penguin.cz \
--cc=zaurus-devel@www.linuxtogo.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
all inboxes | Powered by JetHome®