From: Jerome Brunet <jbrunet@baylibre.com>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>
Subject: Re: [GIT PULL] clk: meson: fixes for v5.2
Date: Thu, 13 Jun 2019 10:19:53 +0200 [thread overview]
Message-ID: <df0dad551db9f344e53db134a3c5a25d5d51ae63.camel@baylibre.com> (raw)
In-Reply-To: <20190612230201.3692F20896@mail.kernel.org>
On Wed, 2019-06-12 at 16:02 -0700, Stephen Boyd wrote:
> Quoting Jerome Brunet (2019-06-11 05:23:33)
> > Dear clock maintainers,
> >
> > Below is a request to pull a couple of fixes on Amlogic clocks for v5.2
> > These are typos in recently added clocks, the most annoying one being in
> > the DT binding identifier on the MPLL50M which is used by the network PLL.
> >
> > Regards
> >
> > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> >
> > Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> >
> > are available in the Git repository at:
> >
> > git://github.com/BayLibre/clk-meson.git tags/clk-meson-5.2-1-fixes
> >
> > for you to fetch changes up to 3ff46efbcd90d3d469de8eddaf03d12293aaa50c:
> >
> > clk: meson: meson8b: fix a typo in the VPU parent names array variable (2019-05-20 12:11:08 +0200)
> >
> > ----------------------------------------------------------------
>
> Thanks. Pulled into clk-next.
>
Hi Stephen,
This was actually meant for clk-fixes
We could probably cope with next, but it would be preferable if the typo in the
bindings was fixed by the 5.2 release.
Thx
Jerome
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-06-13 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 12:23 [GIT PULL] clk: meson: fixes for v5.2 Jerome Brunet
2019-06-12 23:02 ` Stephen Boyd
2019-06-13 8:19 ` Jerome Brunet [this message]
2019-06-13 19:07 ` Kevin Hilman
2019-06-13 20:48 ` 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=df0dad551db9f344e53db134a3c5a25d5d51ae63.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-clk@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;
as well as URLs for NNTP newsgroup(s).