From: Tomoya MORINAGA <tomoya-linux-8lRStDepK8iSL1NxhRU65dBPR1lH4CV8@public.gmane.org>
To: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: Christian Gmeiner
<christian.gmeiner-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Problems with i2c_eg20t
Date: Fri, 21 Oct 2011 09:34:46 +0900 [thread overview]
Message-ID: <4EA0BE26.4070609@dsn.lapis-semi.com> (raw)
In-Reply-To: <20111020232701.GK19115-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
Hi Ben,
(2011/10/21 8:27), Ben Dooks wrote:
> On Tue, Oct 18, 2011 at 09:22:50PM +0900, Tomoya MORINAGA wrote:
>> (2011/10/18 20:16), Christian Gmeiner wrote:
>>
>> Hi, Christian
>>
>>> Hi all
>>>
>>> I am using a 3.0.7 linux kernel with "[PATCH x/7 v4] i2c-eg20t: ..."
>>> from 12. October on top of
>>> it.
>
> Shall I leave v4 on the list of things to submit?
The latest i2c-eg20t.c with v4 patch series works fine both our side
and customer side.
So, I want you to merge v4 series to linux upstream tree.
As to Christian's issue, we will analyze it.
(Unfortunately, we have just involved another task.
So, we can't start soon)
Thanks,
--
tomoya
ROHM Co., Ltd.
next prev parent reply other threads:[~2011-10-21 0:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 11:16 Problems with i2c_eg20t Christian Gmeiner
[not found] ` <CAH9NwWdogRey=hmzjebP9qhX5iOw3rTzdyt2fTWq5C4Z31t=cA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-18 12:22 ` Tomoya MORINAGA
[not found] ` <4E9D6F9A.2060406-8lRStDepK8iSL1NxhRU65dBPR1lH4CV8@public.gmane.org>
2011-10-19 6:44 ` Christian Gmeiner
2011-10-20 23:27 ` Ben Dooks
[not found] ` <20111020232701.GK19115-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2011-10-21 0:34 ` Tomoya MORINAGA [this message]
2011-10-21 7:23 ` Christian Gmeiner
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=4EA0BE26.4070609@dsn.lapis-semi.com \
--to=tomoya-linux-8lrstdepk8isl1nxhru65dbpr1lh4cv8@public.gmane.org \
--cc=ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=christian.gmeiner-Re5JQEeQqe8AvxtiuMwx3w@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