From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch] cleanup spitz battery charging code
Date: Mon, 07 Nov 2005 11:39:44 +0000 [thread overview]
Message-ID: <1131363585.8375.57.camel@localhost.localdomain> (raw)
In-Reply-To: <20051106213054.GI29901@elf.ucw.cz>
On Sun, 2005-11-06 at 22:30 +0100, Pavel Machek wrote:
> This cleans up sharpsl charging code a bit, without really changing
> anything. It will probably break compilation on corgi, but few "()"s
> should fix that, and those macros are *really* evil.
>
> Please apply... rmk said he prefers sharp patches to go through you. I
> hope it is okay with you.
>
> Signed-off-by: Pavel Machek <pavel@suse.cz>
Thanks for this, its fine with me. I've been making changes like this to
bring the driver up to standard for a long time and after a while you
begin to loose site of what else needs doing.
The patch is queued in Russell's patch system. This can be applied once
its fate has been determined.
Richard
prev parent reply other threads:[~2005-11-07 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 21:30 [patch] cleanup spitz battery charging code Pavel Machek
2005-11-07 11:39 ` Richard Purdie [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=1131363585.8375.57.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.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