From: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: Mike Frysinger <vapier.adi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: I2C patch merging for embedded systems
Date: Mon, 1 Jun 2009 23:47:02 +0100 [thread overview]
Message-ID: <20090601224702.GJ14476@trinity.fluff.org> (raw)
In-Reply-To: <8bd0f97a0905312242k451f5492g1a9b3e6d7f7899a3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, Jun 01, 2009 at 01:42:27AM -0400, Mike Frysinger wrote:
> going by MAINTAINERS, Ben Dooks watches over embedded platforms. does
> that mean you'll merge patches posted (e.g. the Blackfin I2C driver),
> or should i merge them through the Blackfin tree ? or will Jean still
> do this via his quilt ?
Even if they are going via the blackfin tree, they need to have been
reviewed on ther i2c list by at-least myself and anyone else interested
in these.
For driver additions, I would prefer if they went via me so that we
don't end up with merge fun in the Kconfig of Makefiles.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2009-06-01 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 5:42 I2C patch merging for embedded systems Mike Frysinger
[not found] ` <8bd0f97a0905312242k451f5492g1a9b3e6d7f7899a3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-01 6:22 ` Jean Delvare
[not found] ` <20090601082213.70701999-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-06-01 6:25 ` Mike Frysinger
2009-06-01 22:47 ` Ben Dooks [this message]
[not found] ` <20090601224702.GJ14476-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2009-06-01 22:49 ` Mike Frysinger
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=20090601224702.GJ14476@trinity.fluff.org \
--to=ben-linux-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vapier.adi-Re5JQEeQqe8AvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.