From: Mike Turquette <mturquette@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Simon Horman <horms@verge.net.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
Subject: Re: linux-next: manual merge of the clk tree with the renesas tree
Date: Wed, 10 Sep 2014 09:56:49 -0700 [thread overview]
Message-ID: <20140910165649.19023.66202@quantum> (raw)
In-Reply-To: <20140910173335.594bf533@canb.auug.org.au>
Quoting Stephen Rothwell (2014-09-10 00:33:35)
> Hi Mike,
>
> Today's linux-next merge of the clk tree got a conflict in
> Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt
> between commit b32c44b93af3 ("clk: shmobile: Add r8a7740, sh73a0 SoCs
> to MSTP bindings") from the renesas tree and commit 5acb7bbbab7c ("ARM:
> shmobile: r8a7794: document MSTP clock support") from the clk tree.
>
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).
We expected this, since the r8a7794 clock stuff is going through the
renesas tree. Looks good to me.
Thanks,
Mike
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
> diff --cc Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt
> index 8f1424f0fa43,a03c8c029a94..000000000000
> --- a/Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt
> +++ b/Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt
> @@@ -15,7 -14,7 +15,8 @@@ Required Properties
> - "renesas,r8a7779-mstp-clocks" for R8A7779 (R-Car H1) MSTP gate clocks
> - "renesas,r8a7790-mstp-clocks" for R8A7790 (R-Car H2) MSTP gate clocks
> - "renesas,r8a7791-mstp-clocks" for R8A7791 (R-Car M2) MSTP gate clocks
> + - "renesas,r8a7794-mstp-clocks" for R8A7794 (R-Car E2) MSTP gate clocks
> + - "renesas,sh73a0-mstp-clocks" for SH73A0 (SH-MobileAG5) MSTP gate clocks
> - "renesas,cpg-mstp-clock" for generic MSTP gate clocks
> - reg: Base address and length of the I/O mapped registers used by the MSTP
> clocks. The first register is the clock control register and is mandatory.
next prev parent reply other threads:[~2014-09-10 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 7:33 linux-next: manual merge of the clk tree with the renesas tree Stephen Rothwell
2014-09-10 16:56 ` Mike Turquette [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-15 6:11 Stephen Rothwell
2014-05-15 6:33 ` Mike Turquette
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=20140910165649.19023.66202@quantum \
--to=mturquette@linaro.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=ulrich.hecht+renesas@gmail.com \
/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).