From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: Vincent Sanders <vince-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org>,
I2C List <i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org>
Subject: Re: i2c-s3c2410: Pass I2C bus number via platform data
Date: Tue, 19 Feb 2008 17:50:51 +0100 [thread overview]
Message-ID: <20080219175051.6c8a0fe5@hyperion.delvare> (raw)
In-Reply-To: <20080212122701.GA15415-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
Hi Ben,
On Tue, 12 Feb 2008 12:27:01 +0000, Ben Dooks wrote:
> On Thu, Jan 31, 2008 at 11:24:53AM +0000, Ben Dooks wrote:
> > Allow the platform data to specify the bus bumber of the
> > I2C bus (or automatically choose one) for the driver.
> >
> > Signed-off-by: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
>
> Did this get lost in the list traffic or should it have
> been sent to someone specific to get it merged during the
> now defunct merge window?
Lost in the traffic, I'm reviewing it just now, sorry.
That being said, you sent this patch on January 31st while I issued my
i2c git pull request to Linus on January 27th, so it was already too
late. If you want changes to go upstream quickly, you shouldn't wait
until the last minute for submitting them. Any change should be
included in at least one -mm (or now linux-next) release before I
consider pushing it upstream!
--
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-02-19 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 11:24 i2c-s3c2410: Pass I2C bus number via platform data Ben Dooks
[not found] ` <20080131112452.859942220-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2008-02-12 12:27 ` Ben Dooks
[not found] ` <20080212122701.GA15415-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2008-02-19 16:50 ` Jean Delvare [this message]
2008-02-19 17:06 ` 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=20080219175051.6c8a0fe5@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=vince-Y5A6D6n0/KfQXOPxS62xeg@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