From: Jean Delvare <khali@linux-fr.org>
To: "Bryan Wu" <cooloney.lkml@gmail.com>
Cc: bryan.wu@analog.com, i2c@lm-sensors.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] Blackfin I2C/TWI driver: update for 2.6.24 merge windows
Date: Fri, 19 Oct 2007 11:07:50 +0200 [thread overview]
Message-ID: <20071019110750.33f66dd8@hyperion.delvare> (raw)
In-Reply-To: <386072610710172311o7d2207f2he47e16c48016c2c2@mail.gmail.com>
Hi Bryan,
On Thu, 18 Oct 2007 14:11:35 +0800, Bryan Wu wrote:
> Could you kindly review this patch?
I'm pretty busy these days, I don't have much spare time for reviews.
BTW, as a rule of thumb, I am ignoring patches that are sent to the
LKML in addition to the i2c list. If you think that your patch is so
important that it has to be send to a list with over 4500 subscribers
that sees 120.000 messages each year, then who am I to dare to comment
on it?
If you want me to consider your patches as something that needs my
attention, send them to the i2c list only, do not add LKML. This is
general advice for everyone sending i2c patches, not just you, of
course.
Back to your patch... Originally you posted two patches, and I see that
they are now merged into a single patch, why? It's much better to have
separate patches, it makes reviews and testing way easier. If you
provide separate patches I'll try to find some time to review them.
Note that this won't be for 2.6.24 anyway, it's too late for that, I've
already sent my i2c patches to Linus. From now on, only bugfixes can go
in 2.6.24, improvements will have to wait for 2.6.25.
--
Jean Delvare
next prev parent reply other threads:[~2007-10-19 9:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 13:53 Bryan Wu
2007-10-18 6:11 ` Bryan Wu
2007-10-19 9:07 ` Jean Delvare [this message]
2007-10-19 9:23 ` Bryan Wu
2007-10-19 10:19 ` Jean Delvare
2007-10-19 9:23 ` Andrew Morton
2007-10-19 11:52 ` Jean Delvare
2007-10-19 12:49 ` Manu Abraham
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=20071019110750.33f66dd8@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=cooloney.lkml@gmail.com \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@vger.kernel.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®