From: Michael Turquette <mturquette@baylibre.com>
To: Kevin Hilman <khilman@baylibre.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>
Cc: "Heiner Kallweit" <hkallweit1@gmail.com>,
"Jerome Brunet" <jbrunet@baylibre.com>,
"Neil Armstrong" <narmstrong@baylibre.com>,
linux-amlogic@lists.infradead.org, linux-crypto@vger.kernel.org,
"Stephen Boyd" <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/3] clk: meson-gxbb: expose clock CLKID_RNG0
Date: Wed, 22 Mar 2017 18:43:50 -0700 [thread overview]
Message-ID: <149023343045.54062.16811894906233729582@resonance> (raw)
In-Reply-To: <m2lgrxnxlz.fsf@baylibre.com>
Quoting Kevin Hilman (2017-03-22 08:24:08)
> Herbert Xu <herbert@gondor.apana.org.au> writes:
>
> > On Thu, Mar 16, 2017 at 11:24:31AM -0700, Kevin Hilman wrote:
> >> Hi Herbert,
> >>
> >> Herbert Xu <herbert@gondor.apana.org.au> writes:
> >>
> >> > On Wed, Feb 22, 2017 at 07:55:24AM +0100, Heiner Kallweit wrote:
> >> >> Expose clock CLKID_RNG0 which is needed for the HW random number generator.
> >> >>
> >> >> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> >> >
> >> > All patches applied. Thanks.
> >>
> >> Actually, can you just apply [PATCH 4/4] to your tree?
> >>
> >> The clock and DT patches need to go through their respective trees or
> >> will otherwise have conflicts with other things going in via those
> >> trees.
> >
> > It's too late now. Please speak up sooner next time. These
> > patches were posted a month ago.
>
> Because this will be causing conflicts with both the platform (amlogic)
> tree and the clk tree, could provide an immutable branch where these are
> applied to help us handle these conflicts?
+1
The DT header changes will cause conflicts in the clk tree. Much better
to either arrange for the patches to be applied by the correct
maintainers or to provide a stable, immutable branch.
Best regards,
Mike
>
> Thanks,
>
> Kevin
next prev parent reply other threads:[~2017-03-23 1:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 6:55 [PATCH v3 1/3] clk: meson-gxbb: expose clock CLKID_RNG0 Heiner Kallweit
2017-02-22 6:59 ` [PATCH v3 2/4] ARM64: dts: meson-gx: add clock to DT binding documentation for hwrng Heiner Kallweit
2017-02-27 22:34 ` Rob Herring
[not found] ` <4e2d12e5-f75b-3ac6-a3f7-18e8a8b7283b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-22 7:00 ` [PATCH v3 3/4] ARM64: dts: meson-gx: add clock CLKID_RNG0 to hwrng node Heiner Kallweit
2017-02-22 7:02 ` [PATCH v3 4/4] hwrng: meson: add clock handling to driver Heiner Kallweit
2017-02-27 13:28 ` [PATCH v3 1/3] clk: meson-gxbb: expose clock CLKID_RNG0 Neil Armstrong
2017-03-16 10:07 ` Herbert Xu
2017-03-16 18:24 ` Kevin Hilman
2017-03-17 8:30 ` Herbert Xu
[not found] ` <20170317083032.GA18512-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org>
2017-03-17 23:05 ` Kevin Hilman
2017-03-22 15:24 ` Kevin Hilman
2017-03-23 1:43 ` Michael Turquette [this message]
2017-03-23 7:56 ` Herbert Xu
2017-03-28 22:07 ` Michael Turquette
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=149023343045.54062.16811894906233729582@resonance \
--to=mturquette@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=hkallweit1@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=sboyd@codeaurora.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).