From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] Broadcom dts changes for 4.11 (part 2)
Date: Tue, 7 Feb 2017 12:59:12 -0800 [thread overview]
Message-ID: <077dc1a1-7069-dd84-5f23-1f88420b05e5@gmail.com> (raw)
In-Reply-To: <1912177.f24aWX6xy5@wuerfel>
On 02/07/2017 06:49 AM, Arnd Bergmann wrote:
> On Wednesday, February 1, 2017 6:06:07 PM CET Florian Fainelli wrote:
>> Please note that because of the "clk" topic branch merged by Eric, we end-up with
>> pulling in v4.10-rc2 which is responsible for the funny diff here.
>
> It's generally better to avoid those back-merges entirely, that is not
> the only problem with them. Our DT branch is already based on -rc3,
> so it's not a back-merged for me, and I think that's ok when I send
> it upstream.
>
> However, I see that you do pull in these changes:
>
> Eric Anholt (5):
> clk: bcm2835: Don't rate change PLLs on behalf of DSI PLL dividers.
> clk: bcm2835: Register the DSI0/DSI1 pixel clocks.
> clk: bcm2835: Add leaf clock measurement support, disabled by default
>
> I'd rather not have those in next/dt at all, and at the very least
> we require an explanation in the changelog about why you are sending
> them to arm-soc. I assume that they are present in the clk-next
> tree and won't get rebased, but that's not clear from your pull
> request.
OK, the explanation is provided in the merge commit, but I suppose I
should have added this again to the pull request changelog.
>
> Are you doing an incompatible DT binding change that requires changing
> the dts files and the driver together? If so, that also needs to be
> in the changelog (or avoided if at all possible).
Eric, do you mind commenting on that part?
>
> If you send the other changes again today, I'll pull them right away,
> and then we can talk about what we do for the clk-bcm2835 changes.
OK, let me try to sync up with Eric on this and see if we can come up
with something better. A pull request based on v4.10-rc3 would be
acceptable, right?
--
Florian
next prev parent reply other threads:[~2017-02-07 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 2:06 [GIT PULL 1/2] Broadcom dts changes for 4.11 (part 2) Florian Fainelli
2017-02-07 14:49 ` Arnd Bergmann
2017-02-07 20:59 ` Florian Fainelli [this message]
2017-02-07 21:12 ` Arnd Bergmann
2017-02-07 23:52 ` Eric Anholt
2017-02-08 9:01 ` Arnd Bergmann
2017-02-09 19:16 ` Florian Fainelli
2017-02-07 21:05 ` Eric Anholt
2017-03-06 4:29 ` Baruch Siach
2017-03-06 6:21 ` Florian Fainelli
-- strict thread matches above, loose matches on Subject: below --
2017-02-02 2:04 Florian Fainelli
2017-02-02 2:06 ` Florian Fainelli
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=077dc1a1-7069-dd84-5f23-1f88420b05e5@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).