Linux-Clk Archive on lore.kernel.org
 help / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: Kevin Hilman <khilman@baylibre.com>,
	Jerome Brunet <jbrunet@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	Jian Hu <jian.hu@amlogic.com>
Subject: Re: [PATCH v6 0/4] clk: meson-g12a: Add EE clock controller driver
Date: Thu, 7 Feb 2019 14:06:52 +0100
Message-ID: <00f67ab3-93a9-9663-586f-e50e69a20902@baylibre.com> (raw)
In-Reply-To: <7hbm3ogshf.fsf@baylibre.com>

On 07/02/2019 04:58, Kevin Hilman wrote:
> Neil Armstrong <narmstrong@baylibre.com> writes:
> 
>> Le 01/02/2019 15:53, Jerome Brunet a écrit :
>>> This purpose of this patchset is to the main clock controller of the
>>> g12a SoC family
>>>
>>> This patchset depends on the recent rework the meson clock directory [7].
> 
> [...]
> 
>> Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
>>
>> I'm applying these to next/drivers for Linux 5.1-rc1, is it necessary to
>> have a tag for the headers ?
> 
> Only if we have some users that we want to merge in the v5.1 cycle
> (which I haven't seen yet.)

Same, we will wait for next cycle then.

Neil

> 
> Kevin
> 


      reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01 14:53 Jerome Brunet
2019-02-01 14:53 ` [PATCH v6 1/4] clk: meson: pll: update driver for the g12a Jerome Brunet
2019-02-01 14:53 ` [PATCH v6 2/4] dt-bindings: clk: meson: add g12a periph clock controller bindings Jerome Brunet
2019-02-01 14:53 ` [PATCH v6 3/4] clk: meson: g12a: add peripheral clock controller Jerome Brunet
2019-02-01 14:53 ` [PATCH v6 4/4] clk: meson: factorise meson64 peripheral clock controller drivers Jerome Brunet
2019-02-02 17:05 ` [PATCH v6 0/4] clk: meson-g12a: Add EE clock controller driver Neil Armstrong
2019-02-07  3:58   ` Kevin Hilman
2019-02-07 13:06     ` Neil Armstrong [this message]

Reply instructions:

You may reply publically 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=00f67ab3-93a9-9663-586f-e50e69a20902@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=jbrunet@baylibre.com \
    --cc=jian.hu@amlogic.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@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

Linux-Clk Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-clk/0 linux-clk/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-clk linux-clk/ https://lore.kernel.org/linux-clk \
		linux-clk@vger.kernel.org linux-clk@archiver.kernel.org
	public-inbox-index linux-clk


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-clk


AGPL code for this site: git clone https://public-inbox.org/ public-inbox