All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>,
	Michael Turquette <mturquette@baylibre.com>
Cc: Kevin Hilman <khilman@gmail.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	"open list:ARM/Amlogic Meson..."
	<linux-amlogic@lists.infradead.org>,
	linux-clk <linux-clk@vger.kernel.org>
Subject: Re: [GIT PULL] clk: meson: update for v5.3
Date: Mon, 24 Jun 2019 17:47:41 -0700	[thread overview]
Message-ID: <20190625004742.74CB9205F4@mail.kernel.org> (raw)
In-Reply-To: <39ccc93ddd8bc64af85541086190e563fa13f038.camel@baylibre.com>

Quoting Jerome Brunet (2019-06-11 05:38:17)
> 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)
> 
> ----------------------------------------------------------------

Thanks. Pulled into clk-next


WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>,
	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: Mon, 24 Jun 2019 17:47:41 -0700	[thread overview]
Message-ID: <20190625004742.74CB9205F4@mail.kernel.org> (raw)
In-Reply-To: <39ccc93ddd8bc64af85541086190e563fa13f038.camel@baylibre.com>

Quoting Jerome Brunet (2019-06-11 05:38:17)
> 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)
> 
> ----------------------------------------------------------------

Thanks. Pulled into clk-next


_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2019-06-25  0:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 12:38 [GIT PULL] clk: meson: update for v5.3 Jerome Brunet
2019-06-11 12:38 ` Jerome Brunet
2019-06-25  0:47 ` Stephen Boyd [this message]
2019-06-25  0:47   ` Stephen Boyd
2019-06-25  8:56 ` Jerome Brunet
2019-06-25  8:56   ` Jerome Brunet
2019-06-25  9:26   ` Jerome Brunet
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=20190625004742.74CB9205F4@mail.kernel.org \
    --to=sboyd@kernel.org \
    --cc=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 \
    /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.