From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Bryan Wu <cooloney-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH 0/6] Blackfin I2C TWI driver updates
Date: Wed, 12 Mar 2008 19:37:18 +0100 [thread overview]
Message-ID: <20080312193718.1aa86caf@hyperion.delvare> (raw)
In-Reply-To: <1205479360-25240-1-git-send-email-cooloney-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Hi Bryan,
On Fri, 14 Mar 2008 00:22:34 -0700, Bryan Wu wrote:
> I reworked this series updates according to you review in previous email.
> Could you please apply these patches to 2.6.25, because Blackfin BF54x compiling
> will fail without these?
No, sorry. We're at rc5 already. If you wanted these changes in 2.6.25,
you should have sent them 2 months ago. Plus, none of the 6 patches in
this series says that it fixes a build failure.
At this point of the release cycle I can only accept build fixes, bug
fixes and documentation updates. If anything like this is needed for
the i2c-bfin-twi driver, please send short, clean, documented patches
that do not depend on other patches, and I'll review and apply them.
Anything else will have to wait until 2.6.26.
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-03-12 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 16:25 [PATCH 0/6] Blackfin I2C TWI driver updates Bryan Wu
[not found] ` <1205479360-25240-1-git-send-email-cooloney-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2008-03-12 18:37 ` Jean Delvare [this message]
[not found] ` <20080312193718.1aa86caf-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-03-13 2:07 ` Bryan Wu
[not found] ` <386072610803121907y499903ban37456d06d36a07a8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-03-13 5:43 ` Kalle Pokki
[not found] ` <Pine.LNX.4.64.0803130726410.26435-er0LZAA46r2WwDxiJSwuDc1vFkv34tBQrE5yTffgRl4@public.gmane.org>
2008-03-13 7:50 ` Bryan Wu
[not found] ` <386072610803130050j47f2659bpbf53199c7dec4916-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-03-13 14:34 ` Jean Delvare
[not found] ` <20080313153412.6c978e24-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-03-13 16:25 ` Bryan Wu
[not found] ` <386072610803130925r3353032kc4e47d4a0948dba4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-03-13 17:13 ` Jean Delvare
2008-03-13 12:03 ` Jean Delvare
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=20080312193718.1aa86caf@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=cooloney-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.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