From: Jerome Brunet <jbrunet@baylibre.com>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: "open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
Kevin Hilman <khilman@gmail.com>,
linux-clk <linux-clk@vger.kernel.org>,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [GIT PULL] clk: meson: update for v5.3
Date: Tue, 25 Jun 2019 10:56:02 +0200 [thread overview]
Message-ID: <1jv9wuyrfh.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <39ccc93ddd8bc64af85541086190e563fa13f038.camel@baylibre.com>
On Tue 11 Jun 2019 at 14:38, Jerome Brunet <jbrunet@baylibre.com> wrote:
> Dear clock maintainers,
>
> Below is a request to pull Amlogic clock update for v5.3 based on the fixes
> we just send. This update add the init() callback to the mpll clock driver
> as discussed in the previous cycle. As promised, the rework to register/deregister
> will follow.
>
> Apart from this, we've got a fairly regular update, adding a bunch of new
> clocks to several SoC families. It also adds support for g12b derived from the
> g12a, which explains the significant line count in the g12a file.
>
> The following changes since commit 3ff46efbcd90d3d469de8eddaf03d12293aaa50c:
>
> clk: meson: meson8b: fix a typo in the VPU parent names array variable (2019-05-20 12:11:08 +0200)
>
> are available in the Git repository at:
>
> git://github.com/BayLibre/clk-meson.git tags/clk-meson-5.3-1
>
> for you to fetch changes up to eda91833f099277998814105c77b5b12cbfab6db:
>
> clk: meson: g12a: mark fclk_div3 as critical (2019-06-11 11:28:44 +0200)
>
Hi Stephen,
Could let us if you intend to take this PR as it is or if you are expecting
any change ?
Best regards
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-25 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 12:38 Jerome Brunet
2019-06-25 0:47 ` Stephen Boyd
2019-06-25 8:56 ` Jerome Brunet [this message]
2019-06-25 9:26 ` Jerome Brunet
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=1jv9wuyrfh.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=khilman@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=narmstrong@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
all inboxes | Powered by JetHome®