From: Jack Daniel <wanders.thirst-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: Kevin Hilman
<khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/6] i2c: davinci updates for 2.6.35
Date: Tue, 3 Aug 2010 12:58:40 +0530 [thread overview]
Message-ID: <AANLkTim=w1VPYPZe62sEdakUDHASFy0EUruRT4z4cpqA@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilL-nD_QVXPGqQbqJMmCNrQvPo_jrKfSrZyDqNb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Ben,
On Wed, Jul 14, 2010 at 9:04 PM, Jack Daniel <wanders.thirst-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On Mon, Apr 19, 2010 at 5:06 PM, Ben Dooks <ben-li...-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org> wrote:
>> On Tue, Apr 06, 2010 at 10:42:12AM -0700, Kevin Hilman wrote:
>>> This series of davinci I2C driver updates and fixes is targetted for
>>> 2.6.35. It has been tested in davinci git on multiple davinci SoCs.
>>>
>>> Ben, since these changes are isolated to the davinci driver only, if
>>> you prefer I can merge them upstream along with my davinci changes for
>>> 2.6.35.
>>
>> I'll get them into -next when I rebase it.
>
>>Ben, this series never made it in for 2.6.35.
>
>>I've now rebased this against v2.6.35-rc3 and it's available here:
>
>> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-davinci.git
>>davinci-i2c
>
>>Please pull for 2.6.36. Thanks.
>
>>Kevin
>
> Would like to know when this bug fix "i2c: davinci: Fix smbus Oops
> with AIC33 usage" will be included? I can't find it in the 2.6.35-rc5
> of Linus tree.
This has not made it to 2.6.35, pray tell what might be the reason for
its non-inclusion? Your tree is still at 2.6.34-rc5, are you not
taking any more patches? You did not reply to my previous mail,
perhaps you did not like the fact that I use a forwarded mail ? This
was because I did not subscribe to the i2c mailing list and had to
copy the message. I know of no other way.
Thanks and regards,
Jack.
next prev parent reply other threads:[~2010-08-03 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 15:34 [PATCH 0/6] i2c: davinci updates for 2.6.35 Jack Daniel
[not found] ` <AANLkTilL-nD_QVXPGqQbqJMmCNrQvPo_jrKfSrZyDqNb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-03 7:28 ` Jack Daniel [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-06 17:42 Kevin Hilman
[not found] ` <1270575738-22388-1-git-send-email-khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2010-04-20 0:06 ` Ben Dooks
[not found] ` <20100420000621.GK32401-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2010-04-20 13:55 ` Kevin Hilman
2010-06-21 20:16 ` Kevin Hilman
[not found] ` <AANLkTikJ6XDywcBA5O0mC85jQEIWxZ9NOALIQOjcGCDJ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-10 15:56 ` Kevin Hilman
[not found] ` <AANLkTinNXxzCoH+b3=xA92sW8GCqqO4iY+_yVwBFLMqG-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-10 23:44 ` Ben Dooks
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='AANLkTim=w1VPYPZe62sEdakUDHASFy0EUruRT4z4cpqA@mail.gmail.com' \
--to=wanders.thirst-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).