From: Ben Dooks <ben-linux@fluff.org>
To: Timur Tabi <timur@freescale.com>
Cc: Jean Delvare <khali@linux-fr.org>,
linuxppc-dev@ozlabs.org, Kumar Gala <kumar.gala@freescale.com>,
linux-i2c@vger.kernel.org, Ben Dooks <ben-linux@fluff.org>
Subject: Re: [PATCH] i2c-mpc: do not allow interruptions when waiting for I2C to complete
Date: Wed, 11 Feb 2009 00:16:36 +0000 [thread overview]
Message-ID: <20090211001636.GA19758@fluff.org.uk> (raw)
In-Reply-To: <4991A970.70508@freescale.com>
On Tue, Feb 10, 2009 at 10:21:04AM -0600, Timur Tabi wrote:
> Jean Delvare wrote:
>
> > To the best of my knowledge i2c-mpc falls into the "embedded platforms"
> > category and is thus under Ben's responsibility.
>
> I don't see his Signed-off-by on any patch to i2c-mpc.c for the past
> three years (at least). I do see yours, however. You have directly
> applied similar patches in the recent past, so of course I will assume
> that you would apply this one.
My appointment as an embedded maintainer is relatively recent.
I do try and review patches, and sometimes these patches get sent
to another maintainer.
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2009-02-11 0:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 14:00 [PATCH] i2c-mpc: do not allow interruptions when waiting for I2C to complete Timur Tabi
2009-02-10 14:59 ` Timur Tabi
2009-02-10 15:55 ` Jean Delvare
2009-02-10 16:01 ` Timur Tabi
2009-02-10 16:10 ` Jean Delvare
2009-02-10 16:21 ` Timur Tabi
2009-02-10 16:28 ` Wolfram Sang
2009-02-11 0:16 ` Ben Dooks [this message]
2009-02-10 15:11 ` Wolfram Sang
2009-02-11 0:17 ` Ben Dooks
2009-02-19 16:41 ` Kumar Gala
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=20090211001636.GA19758@fluff.org.uk \
--to=ben-linux@fluff.org \
--cc=khali@linux-fr.org \
--cc=kumar.gala@freescale.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.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).