From: Michael Turquette <mturquette@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
"Stephen Boyd" <sboyd@codeaurora.org>
Cc: "Simon Horman" <horms@verge.net.au>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Ulrich Hecht" <ulrich.hecht+renesas@gmail.com>,
linux-clk@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [git pull] clk/shmobile updates for v4.2
Date: Tue, 09 Jun 2015 19:47:17 -0700 [thread overview]
Message-ID: <20150610024717.6017.50093@quantum> (raw)
In-Reply-To: <1433244779-5447-1-git-send-email-geert+renesas@glider.be>
Quoting Geert Uytterhoeven (2015-06-02 04:32:59)
> Hi Mike, Stephen,
> =
> The following changes since commit c65b99f046843d2455aa231747b5a07a999a9f=
3d:
> =
> Linux 4.1-rc6 (2015-05-31 19:01:07 -0700)
> =
> are available in the git repository at:
> =
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git=
clk-shmobile-for-4.2
Pulled!
FYI, I prefer to take PRs based on -rc1 if possible. This PR forced me
to update clk-next which was previously based on -rc1 (I merged clk-next
into -rc7 and then pulled your tag).
Of course some times this is unavoidable, due to a dependency on a fix
in a recent -rc.
Regards,
Mike
> =
> for you to fetch changes up to a431c1fa01ff020ecb146c04fbbea974e3eb910f:
> =
> clk: shmobile: rz: Document mandatory compatible fallback (2015-06-01 1=
2:25:28 +0200)
> =
> Summary:
> =
> Updates for existing shmobile DT clock bindings:
> - Add support for new SoCs, following existing practices,
> - Document compatible fallbacks that are mandatory, because the driver
> matches against the generic fallback only.
> =
> Thanks for pulling!
> =
> ----------------------------------------------------------------
> Geert Uytterhoeven (5):
> clk: shmobile: r8a7794: Document DIV6 clock bindings
> clk: shmobile: div6: Document mandatory compatible fallback
> clk: shmobile: mstp: Document mandatory compatible fallback
> clk: shmobile: rcar-gen2: Document mandatory compatible fallback
> clk: shmobile: rz: Document mandatory compatible fallback
> =
> Ulrich Hecht (3):
> clk: shmobile: Add r8a7778 SoC to MSTP bindings
> clk: shmobile: Add r8a7793 SoC to MSTP bindings
> clk: shmobile: r8a7793: Document DIV6 clock bindings
> =
> Documentation/devicetree/bindings/clock/renesas,cpg-div6-clocks.txt | 6 =
++++--
> Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt | 6 =
++++--
> .../devicetree/bindings/clock/renesas,rcar-gen2-cpg-clocks.txt | 2 =
+-
> Documentation/devicetree/bindings/clock/renesas,rz-cpg-clocks.txt | 2 =
+-
> 4 files changed, 10 insertions(+), 6 deletions(-)
> =
> Gr{oetje,eeting}s,
> =
> Geert
> =
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6=
8k.org
> =
> In personal conversations with technical people, I call myself a hacker. =
But
> when I'm talking to journalists I just say "programmer" or something like=
that.
> -- Linus Torv=
alds
next prev parent reply other threads:[~2015-06-10 2:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 11:32 [git pull] clk/shmobile updates for v4.2 Geert Uytterhoeven
2015-06-10 2:47 ` Michael Turquette [this message]
2015-06-10 5:08 ` Geert Uytterhoeven
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=20150610024717.6017.50093@quantum \
--to=mturquette@linaro.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-clk@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=sboyd@codeaurora.org \
--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