mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Eric Miao <eric.y.miao@gmail.com>
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, utx@penguin.cz
Subject: Re: zaurus: cleanup sharpsl_pm.c
Date: Thu, 22 Oct 2009 21:19:55 +0200	[thread overview]
Message-ID: <20091022191954.GB6611@elf.ucw.cz> (raw)
In-Reply-To: <f17812d70910221126k50c4ea7em9d58f6e85db884ae@mail.gmail.com>

On Fri 2009-10-23 02:26:55, Eric Miao wrote:
> > Introduce separate set of battery limits for corgi. This fixes
> > compilation, and the values probably should be subtly different, too.
> 
> [Why I'm receiving this for twice ....?]

No idea. Perhaps once from maillist?

> Pavel,
> 
> Anyway, I was thinkin maybe we need a shared table before there
> are real requirements for different machines to have their own?

Well, I'd say that the sharing leads to some very ugly code. ... so
I'd preer it unshared.

But if you would prefer, I can prepare patch without the table
moving...?

								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-10-22 19:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 20:03 Pavel Machek
2009-10-17 16:36 ` Pavel Machek
2009-10-20 15:59   ` Eric Miao
2009-10-22 14:05     ` Eric Miao
2009-10-22 17:48       ` Pavel Machek
2009-10-22 18:26         ` Eric Miao
2009-10-22 19:19           ` Pavel Machek [this message]
2009-10-22 19:28             ` Eric Miao
2009-10-22 19:35               ` Pavel Machek
2009-10-22 19:49                 ` Eric Miao
2009-10-22 22:40         ` Richard Purdie

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=20091022191954.GB6611@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Dirk@opfer-online.de \
    --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=metan@ucw.cz \
    --cc=omegamoon@gmail.com \
    --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

all inboxes | Powered by JetHome®