From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, Jian Hu <jian.hu@amlogic.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v6 0/4] clk: meson-g12a: Add EE clock controller driver
Date: Wed, 06 Feb 2019 19:58:04 -0800 [thread overview]
Message-ID: <7hbm3ogshf.fsf@baylibre.com> (raw)
In-Reply-To: <5C55CDCE.9030502@baylibre.com>
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.)
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@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: Wed, 06 Feb 2019 19:58:04 -0800 [thread overview]
Message-ID: <7hbm3ogshf.fsf@baylibre.com> (raw)
In-Reply-To: <5C55CDCE.9030502@baylibre.com>
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.)
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, Jian Hu <jian.hu@amlogic.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v6 0/4] clk: meson-g12a: Add EE clock controller driver
Date: Wed, 06 Feb 2019 19:58:04 -0800 [thread overview]
Message-ID: <7hbm3ogshf.fsf@baylibre.com> (raw)
In-Reply-To: <5C55CDCE.9030502@baylibre.com>
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.)
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-07 3:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 14:53 [PATCH v6 0/4] clk: meson-g12a: Add EE clock controller driver Jerome Brunet
2019-02-01 14:53 ` Jerome Brunet
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 ` Jerome Brunet
2019-02-01 14:53 ` 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 ` Jerome Brunet
2019-02-01 14:53 ` 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 ` Jerome Brunet
2019-02-01 14:53 ` Jerome Brunet
2019-02-01 14:53 ` [PATCH v6 4/4] clk: meson: factorise meson64 peripheral clock controller drivers Jerome Brunet
2019-02-01 14:53 ` Jerome Brunet
2019-02-01 14:53 ` Jerome Brunet
2019-02-02 17:05 ` [PATCH v6 0/4] clk: meson-g12a: Add EE clock controller driver Neil Armstrong
2019-02-02 17:05 ` Neil Armstrong
2019-02-02 17:05 ` Neil Armstrong
2019-02-07 3:58 ` Kevin Hilman [this message]
2019-02-07 3:58 ` Kevin Hilman
2019-02-07 3:58 ` Kevin Hilman
2019-02-07 13:06 ` Neil Armstrong
2019-02-07 13:06 ` Neil Armstrong
2019-02-07 13:06 ` Neil Armstrong
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=7hbm3ogshf.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=jbrunet@baylibre.com \
--cc=jian.hu@amlogic.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=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 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.