From: Len Brown <lenb@kernel.org>
To: "Lebedev, Vladimir P" <vladimir.p.lebedev@intel.com>
Cc: "Starikovskiy, Alexey Y" <alexey.y.starikovskiy@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: battery driver
Date: Fri, 26 Jan 2007 14:43:32 -0500 [thread overview]
Message-ID: <200701261443.33139.lenb@kernel.org> (raw)
In-Reply-To: <8E389A5F2FEABA4CB1DEC35A25CB39CE7836C0@mssmsx411>
On Friday 24 November 2006 12:27, Lebedev, Vladimir P wrote:
> Len,
>
> Attached patch contains new release of battery driver. The battery
> driver was restructured and it is ready now for future development: for
> example: porting from procfs to sysfs. Patch is based on 2.6.19-rc6-mm1.
> It was tested on few laptops on such functionality as: system
> suspend/resume + removing/inserting and so on. I suggest add patch to mm
> tree.
Same comment as for sbs.
It is not practical to review (and thus apply) this patch --
over 800 lines changed with no check-in comment about
what changed or why, no new comments in the code,
tons of whitespace changes, re-names, and apparently
code moving around inside the file.
This needs to be broken up in to a series of patches --
each making a single logical change. each change needs
a check-in comment telling the reviewer exactly what to
expect when reading the patch. cosmetic changes must
never be mixed in the same patch as functional changes --
else it makes the functional change harder to review
and backport.
I'd rather have a series of 80 simple patches of 10 lines
than a single patch of 800 lines. That makes reviewing
easy, and it makes bisect and isolation of regressions easy --
and that is what we need to optimize for.
So download quilt or stgit and learn to use it.
I'm sorry I didn't see this patch when you sent it 8 weeks ago
so I could tell you this right away. However, the good news
is that battery.c has seen only trivial changes since.
thanks,
-Len
next prev parent reply other threads:[~2007-01-26 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 17:27 battery driver Lebedev, Vladimir P
2007-01-26 19:43 ` Len Brown [this message]
2007-02-07 20:07 ` Bugs fixing Lebedev, Vladimir P
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=200701261443.33139.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=alexey.y.starikovskiy@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=vladimir.p.lebedev@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).