From: "Heiko Stübner" <heiko@sntech.de>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [GIT PULL] Rockchip clock updates for 5.1
Date: Fri, 15 Feb 2019 11:32:45 +0100 [thread overview]
Message-ID: <2268273.zyHXOlfcUi@diego> (raw)
In-Reply-To: <154940450309.169292.16565688865245958654@swboyd.mtv.corp.google.com>
Am Dienstag, 5. Februar 2019, 23:08:23 CET schrieb Stephen Boyd:
> Quoting Heiko Stuebner (2019-02-01 03:17:47)
>
> > Hi Mike, Stephen,
> >
> > looks I can re-use my introduction from 4.20 and 5.0 - no big changes
> > again this time.
> >
> > A rate_parent flag and some fixup for the fractional part of a PLL
> >
> > So please pull.
>
> Thanks. Pulled into clk-next. If you like I can pick patches directly
> from list if you send out a reviewed-by tag on the patches. I'm happy
> either way.
It's hard to determine that before each cycle :-) .
The upside right now is, that handling clock-ids gets very easy.
Shared branches between trees for dt-binding ids are not favored,
instead the way to go seems to be doing numbers first and replacing
them in the next cycle when the ids got merged.
Right now I'm also in control of the shared id-branch, merging it myself
into both clock and dts branches, which somehow seems to still be ok,
and hence I save a bit of work :-D .
But of course we can merge the real easy things directly into the clock
tree ... I'll keep that in mind for the next clock patches.
Heiko
prev parent reply other threads:[~2019-02-15 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 11:17 [GIT PULL] Rockchip clock updates for 5.1 Heiko Stuebner
2019-02-05 22:08 ` Stephen Boyd
2019-02-15 10:32 ` Heiko Stübner [this message]
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=2268273.zyHXOlfcUi@diego \
--to=heiko@sntech.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).