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 v5.10-rc1
Date: Tue, 22 Sep 2020 09:39:39 +0200 [thread overview]
Message-ID: <20200922073939.GA3994831@ulmo> (raw)
In-Reply-To: <160072205823.4188128.2973025738875931354@swboyd.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 2652 bytes --]
On Mon, Sep 21, 2020 at 02:00:58PM -0700, Stephen Boyd wrote:
> Quoting Thierry Reding (2020-09-21 05:18:42)
> > On Mon, Sep 21, 2020 at 02:16:28PM +0200, Thierry Reding wrote:
> > > Hi Mike, Stephen,
> > >
> > > The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
> > >
> > > Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
> > >
> > > are available in the Git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/for-5.10-clk
> > >
> > > for you to fetch changes up to 2f878d04218c8b26f6d0ab26955ca6b03848a1ad:
> > >
> > > clk: tegra: Fix missing prototype for tegra210_clk_register_emc() (2020-09-21 14:09:10 +0200)
> > >
> > > Thanks,
> > > Thierry
> > >
> > > ----------------------------------------------------------------
> > > clk: tegra: Changes for v5.10-rc1
> > >
> > > This is a set of small fixes for the Tegra clock driver.
> > >
> > > ----------------------------------------------------------------
> > > Thierry Reding (3):
> > > clk: tegra: Capitalization fixes
> > > clk: tegra: Always program PLL_E when enabled
> > > clk: tegra: Fix missing prototype for tegra210_clk_register_emc()
> > >
> > > drivers/clk/tegra/clk-pll.c | 7 ++-----
> > > drivers/clk/tegra/clk-tegra210-emc.c | 2 ++
> > > 2 files changed, 4 insertions(+), 5 deletions(-)
> >
> > I just realized after sending this out that this is all really tiny and
> > minor fixes, so perhaps it makes sense to even apply this for v5.9?
> >
>
> Is something critical? If so then it's OK to merge for v5.9, otherwise
> I'd rather let it cook in -next for a while. Being small doesn't really
> make a difference here. What matters is that it fixes some critical
> problem, preferably introduced this merge window but if it's annoying
> enough that rule can be broken.
This is actually a subset of a set of patches that I had sitting on a
for-5.9/clk branch but for which I forgot to send a pull request. This
was pointed out to me on IRC yesterday. So this should already be soft-
boiled.
The first patch is just a tiny bit of cleanup, but the second patch
fixes a real problem with SATA that can happen depending on how the
bootloader has set up the PLL_E. The third patch fixes a build
warning, which admittedly isn't critical, but certainly nice to have.
Given that the latter two are the only known issues with the clock
driver I think it would be nice to have them in v5.9, especially since
that's going to be an LTS and we'll end up back-porting at least two of
these patches to it anyway.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-22 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 12:16 [GIT PULL] clk: tegra: Changes for v5.10-rc1 Thierry Reding
2020-09-21 12:18 ` Thierry Reding
2020-09-21 21:00 ` Stephen Boyd
2020-09-22 7:39 ` Thierry Reding [this message]
2020-09-22 19:08 ` Stephen Boyd
2020-09-23 8:12 ` Thierry Reding
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=20200922073939.GA3994831@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox