From: Thierry Reding <thierry.reding@gmail.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [GIT PULL] clk: tegra: Changes for v4.21-rc1
Date: Mon, 10 Dec 2018 12:05:56 +0100 [thread overview]
Message-ID: <20181210110556.GM15154@ulmo> (raw)
In-Reply-To: <154420452153.57851.10805463686191930083@swboyd.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
On Fri, Dec 07, 2018 at 09:42:01AM -0800, Stephen Boyd wrote:
> Quoting Thierry Reding (2018-12-07 06:21:19)
> > Hi Michael, Stephen,
> >
> > The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
> >
> > Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.21-clk
> >
> > for you to fetch changes up to d14ce174ca02ee2a9f390b9e279663b3a848a48b:
> >
> > clk: tegra20: Check whether direct PLLM sourcing is turned off for EMC (2018-11-08 12:47:18 +0100)
> >
> > Turns out that these were not build-time dependencies for the EMC series
> > after all, but since I already have them in a branch, I might as well
> > send them out.
>
> Ok. There were other Tegra patches on the list which I guess I can just
> pick up on top of this tag?
Yes, correct. I'm not aware of any conflicts between these two patches
and the others on the list.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-10 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 14:21 [GIT PULL] clk: tegra: Changes for v4.21-rc1 Thierry Reding
2018-12-07 17:42 ` Stephen Boyd
2018-12-10 11:05 ` Thierry Reding [this message]
2018-12-10 19:09 ` Stephen Boyd
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=20181210110556.GM15154@ulmo \
--to=thierry.reding@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.