From: Stephen Boyd <sboyd@codeaurora.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [GIT PULL v2] clk: tegra: Changes for v4.15-rc1
Date: Tue, 14 Nov 2017 09:55:26 -0800 [thread overview]
Message-ID: <20171114175526.GZ11955@codeaurora.org> (raw)
In-Reply-To: <20171107152532.13918-1-thierry.reding@gmail.com>
On 11/07, Thierry Reding wrote:
> Hi Michael, Stephen,
>
> The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
>
> Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.15-clk-2
>
> for you to fetch changes up to 22ef01a203d27fee8b7694020b7e722db7efd2a7:
>
> clk: tegra: Use readl_relaxed_poll_timeout_atomic() in tegra210_clock_init() (2017-11-01 15:00:07 +0100)
>
> Note that this pulls in parts from two other tags that are going to go
> in via the ARM SoC tree. Those are needed to a couple of resolve build
> dependencies.
>
> This is the follow-up pull request that includes Jon's fix for the pclk
> issue.
Thanks. Pulled into clk-next.
>
> Thanks,
> Thierry
>
> ----------------------------------------------------------------
> clk: tegra: Changes for v4.15-rc1
>
> This contains cleanups and minor fixes for the Tegra clock driver.
>
Please try to be a bit more descriptive here. I use these tag
messages for the overall PR to linus and it makes it easier if I
don't have to dig through all the commits to summarize up.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-11-14 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 15:25 [GIT PULL v2] clk: tegra: Changes for v4.15-rc1 Thierry Reding
2017-11-14 17:55 ` 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=20171114175526.GZ11955@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=thierry.reding@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).