From: Wolfram Sang <wsa@the-dreams.de>
To: Kuninori Morimoto
<kuninori.morimoto.gx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Simon <horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>,
Morimoto
<kuninori.morimoto.gx-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>,
Linux-SH <linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux-I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 0/5] i2c: rcar: add renesas,i2c-rcar-gen1/gen2 in DT compatible
Date: Wed, 06 Aug 2014 19:04:10 +0000 [thread overview]
Message-ID: <20140806190410.GC2736@katana> (raw)
In-Reply-To: <87silaw7t2.wl%kuninori.morimoto.gx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
On Tue, Aug 05, 2014 at 09:39:27PM -0700, Kuninori Morimoto wrote:
>
> Hi Wolfram, Simon
>
> These patches add R-Car generatoin level
> DT compatible on i2c-rcar driver and platform.
>
> Kuninori Morimoto (5):
> i2c: rcar: add renesas,i2c-rcar-gen1/gen2 in DT compatible
> ARM: shmobile: r8a7778: add generation level compatible for i2c
> ARM: shmobile: r8a7779: add generation level compatible for i2c
> ARM: shmobile: r8a7790: add generation level compatible for i2c
> ARM: shmobile: r8a7791: add generation level compatible for i2c
All patches:
Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Simon: Shall I take patch 1?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-06 19:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 4:39 [PATCH 0/5] i2c: rcar: add renesas,i2c-rcar-gen1/gen2 in DT compatible Kuninori Morimoto
[not found] ` <87silaw7t2.wl%kuninori.morimoto.gx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-08-06 4:40 ` [PATCH 1/5] " Kuninori Morimoto
[not found] ` <87r40uw7rp.wl%kuninori.morimoto.gx-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2014-08-07 0:18 ` Simon Horman
2014-08-07 0:36 ` Kuninori Morimoto
[not found] ` <8761i5kuel.wl%kuninori.morimoto.gx-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2014-08-07 1:10 ` Simon Horman
[not found] ` <20140807011025.GA3284-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2014-08-07 2:43 ` Kuninori Morimoto
2014-08-07 3:55 ` Magnus Damm
[not found] ` <CANqRtoSu2cZyY2YELUzPF86UAz+=TFtBYsnmotpNDEh9FEhp1Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-07 5:19 ` Kuninori Morimoto
2014-08-07 5:58 ` Magnus Damm
2014-08-07 8:34 ` Kuninori Morimoto
2014-09-19 17:18 ` Wolfram Sang
2014-09-22 2:04 ` Simon Horman
2014-08-06 4:40 ` [PATCH 2/5] ARM: shmobile: r8a7778: add generation level compatible for i2c Kuninori Morimoto
2014-08-06 19:04 ` Wolfram Sang [this message]
2014-08-06 4:40 ` [PATCH 3/5] ARM: shmobile: r8a7779: " Kuninori Morimoto
2014-08-06 4:40 ` [PATCH 4/5] ARM: shmobile: r8a7790: " Kuninori Morimoto
2014-08-06 4:40 ` [PATCH 5/5] ARM: shmobile: r8a7791: " Kuninori Morimoto
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=20140806190410.GC2736@katana \
--to=wsa@the-dreams.de \
--cc=horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org \
--cc=kuninori.morimoto.gx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kuninori.morimoto.gx-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-sh-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).