From: Ben Dooks <ben-i2c@fluff.org>
To: Kyungmin Park <kmpark@infradead.org>
Cc: Ben Dooks <ben-i2c@fluff.org>, Jean Delvare <khali@linux-fr.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux I2C <linux-i2c@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] i2c fixes for 2.6.36
Date: Wed, 6 Oct 2010 23:12:58 +0100 [thread overview]
Message-ID: <20101006221258.GV21564@trinity.fluff.org> (raw)
In-Reply-To: <AANLkTikvXe5ZHCqqtfkAWu=78HWe0BD=suDMGETwd+hC@mail.gmail.com>
On Fri, Oct 01, 2010 at 11:18:49PM +0900, Kyungmin Park wrote:
> On Fri, Oct 1, 2010 at 11:09 PM, Ben Dooks <ben-i2c@fluff.org> wrote:
> > On Fri, Oct 01, 2010 at 10:38:46PM +0900, Kyungmin Park wrote:
> >> Hi Jean,
> >>
> >> Even though it's not yet acked from Ben. It should be fixed for
> >> correct operation.
> >> Without this patch, some I2C device doesn't work correctly.
> >> http://www.spinics.net/lists/linux-i2c/msg04016.html
> >
> > It was in my last pull request to Linus.
> Thanks Ben,
>
> To Ben,
> Do you have a plan to use notification mail or confirm mail to ensure
> these patches are merged or not.
> I think it's helpful to your maintained subsystem participants. e.g,
> samsung soc, sdhci-s3c, i2c and so on.
I do try and send confirmation emails with every patch, but it currently
is a manual process.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2010-10-06 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 12:06 [GIT PULL] i2c fixes for 2.6.36 Jean Delvare
2010-10-01 13:38 ` Kyungmin Park
2010-10-01 13:47 ` Jean Delvare
2010-10-01 14:09 ` Ben Dooks
2010-10-01 14:18 ` Kyungmin Park
2010-10-06 22:12 ` Ben Dooks [this message]
2010-10-06 21:24 ` 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=20101006221258.GV21564@trinity.fluff.org \
--to=ben-i2c@fluff.org \
--cc=khali@linux-fr.org \
--cc=kmpark@infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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