From: Darius <augulis.darius-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Darius
<public-augulis.darius-Re5JQEeQqe8AvxtiuMwx3w-8ByrlEUxsivZ+VzJOa5vwg@public.gmane.org>,
public-linux-i2c-u79uwXL29TY76Z2rM5mHXA-8ByrlEUxsivZ+VzJOa5vwg@public.gmane.org,
Ben Dooks
<public-ben-linux-elnMNo+KYs3YtjvyW6yDsg-8ByrlEUxsivZ+VzJOa5vwg@public.gmane.org>
Subject: Re: [PATCH v5] iMX/MXC support for I2C
Date: Tue, 17 Feb 2009 09:36:29 +0200 [thread overview]
Message-ID: <499A68FD.3080406@gmail.com> (raw)
In-Reply-To: <20090204100022.GC3084-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Wolfram Sang wrote:
> On Fri, Jan 30, 2009 at 10:32:28AM +0200, Darius wrote:
>
>> From: Darius Augulis <augulis.darius-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>>
>> Implementation of I2C Adapter/Algorithm Driver for I2C Bus integrated
>> in Freescale's i.MX/MXC processors.
>>
>> Signed-off-by: Darius Augulis <augulis.darius-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> Tested-by: Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
>> Reviewed-by: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
>
> Ben, do you pick it up, or should it go via Sascha's iMX-Tree?
>
> Regards,
>
> Wolfram
>
Are there any news from Ben?
next prev parent reply other threads:[~2009-02-17 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 8:32 [PATCH v5] iMX/MXC support for I2C Darius
[not found] ` <4982BB1C.2040508-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-01-30 8:36 ` Darius
2009-02-04 10:00 ` Wolfram Sang
[not found] ` <20090204100022.GC3084-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-02-17 7:36 ` Darius [this message]
2009-02-18 11:52 ` Wolfram Sang
[not found] ` <20090218115252.GB3049-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-02-20 15:09 ` Wolfram Sang
[not found] ` <20090220150905.GC9203-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-03-03 7:16 ` Darius
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=499A68FD.3080406@gmail.com \
--to=augulis.darius-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=public-augulis.darius-Re5JQEeQqe8AvxtiuMwx3w-8ByrlEUxsivZ+VzJOa5vwg@public.gmane.org \
--cc=public-ben-linux-elnMNo+KYs3YtjvyW6yDsg-8ByrlEUxsivZ+VzJOa5vwg@public.gmane.org \
--cc=public-linux-i2c-u79uwXL29TY76Z2rM5mHXA-8ByrlEUxsivZ+VzJOa5vwg@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