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.16
Date: Thu, 21 Dec 2017 16:33:33 -0800 [thread overview]
Message-ID: <20171222003333.GU7997@codeaurora.org> (raw)
In-Reply-To: <1513330717-16712-1-git-send-email-geert+renesas@glider.be>
On 12/15, Geert Uytterhoeven wrote:
> Hi Mike, Stephen,
>
> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
>
> Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
>
> 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.16-tag1
>
> for you to fetch changes up to 7aff266552d6042b43d3d5a9b13f0009ef862033:
>
> clk: renesas: cpg-mssr: Keep wakeup sources active during system suspend (2017-12-14 16:40:36 +0100)
>
> ----------------------------------------------------------------
> clk: renesas: Updates for v4.16
>
> - Add support for the LVDS module clock on R-Car V3M,
> - Keep wakeup sources in Clock Domains active during system suspend,
> which will allow removing workarounds from drivers later.
>
> Thanks for pulling!
>
> P.S. There seems to be issues with kernel.org mirrorring. I can't see my
> tag in the public repo, but the clk-renesas-for-v4.16 branch is
> up-to-date (last change 18 hours ago).
Thanks. Pulled into clk-next.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-12-22 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 9:38 [git pull] clk: renesas: Updates for v4.16 Geert Uytterhoeven
2017-12-22 0:33 ` 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=20171222003333.GU7997@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).