linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [git pull] clk: renesas: Updates for v4.14
Date: Wed, 23 Aug 2017 15:42:16 -0700	[thread overview]
Message-ID: <20170823224216.GH21656@codeaurora.org> (raw)
In-Reply-To: <1502958542-2900-1-git-send-email-geert+renesas@glider.be>

On 08/17, Geert Uytterhoeven wrote:
> 	Hi Mike, Stephen,
> 
> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
> 
>   Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git tags/clk-renesas-for-v4.14-tag1
> 
> for you to fetch changes up to c29f82951b974f27e0bc4ce2525db164f86f2e4d:
> 
>   clk: renesas: r8a7796: Add USB3.0 clock (2017-08-17 09:22:26 +0200)
> 
> ----------------------------------------------------------------
> A bit delayed due to holidays, but here they are!
> 
> clk: renesas: Updates for v4.14
> 
>   - Add more module clocks for R-Car V2H and M3-W,
>   - Add support for the R-Car Gen3 USB 2.0 clock selector PHY,
>   - Add support for the new R-Car D3 SoC,
>   - Allow compile-testing of all (sub)drivers now all dummy infrastructure
>     is available,
>   - Small fixes and cleanups.
> 

Thanks. Pulled into clk-next.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

      reply	other threads:[~2017-08-23 22:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17  8:29 [git pull] clk: renesas: Updates for v4.14 Geert Uytterhoeven
2017-08-23 22:42 ` Stephen Boyd [this message]

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=20170823224216.GH21656@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mturquette@baylibre.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).