From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] arm: shmobile: r8a7790: Fix I2C controller names
Date: Thu, 19 Dec 2013 08:58:11 +0000 [thread overview]
Message-ID: <20131219085808.GC12239@verge.net.au> (raw)
In-Reply-To: <1387379302-20223-1-git-send-email-valentine.barshak@cogentembedded.com>
On Wed, Dec 18, 2013 at 09:17:05PM -0800, Kuninori Morimoto wrote:
>
> Hi
>
> > The R8A7790 is an R-Car Gen2 SoC. The clock division factor
> > (CDF) width is 3 bits on Gen2 as opposed to 2 bits on Gen1.
> > Fix the device names for R8A7790 SoC to make the R-Car I2C
> > driver configure the hardware properly.
> >
> > Signed-off-by: Valentine Barshak <valentine.barshak@cogentembedded.com>
> > ---
>
> Grr... this is correct
> sorry my fault.
>
> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>
> Simon, this patch is based on below patch
>
> 043a3f113ce41e3e6fdbb49551df75e82e8c4ae7
> (i2c: rcar: fixup rcar type naming)
Thanks.
Valentine could you please:
1. Rebase this on the fixes-for-v3.13 branch in the renesas tree and;
2. Include something like this in the following.
This resolves a regression which was introduced by
043a3f113ce41e3 ("i2c: rcar: fixup rcar type naming") in v3.12-rc4.
Thanks.
next prev parent reply other threads:[~2013-12-19 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 15:08 [PATCH] arm: shmobile: r8a7790: Fix I2C controller names Valentine Barshak
2013-12-19 5:17 ` Kuninori Morimoto
2013-12-19 8:58 ` Simon Horman [this message]
2013-12-19 12:24 ` Valentine
2013-12-19 12:35 ` Valentine
2013-12-27 2:10 ` Simon Horman
2013-12-27 10:59 ` Valentine
-- strict thread matches above, loose matches on Subject: below --
2014-01-10 2:45 [GIT PULL] Renesas ARM Based SoC Fixes for v3.14 Simon Horman
2014-01-10 2:46 ` [PATCH] ARM: shmobile: r8a7790: Fix I2C controller names Simon Horman
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=20131219085808.GC12239@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.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).