From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] Broadcom dts changes for 4.11 (part 2)
Date: Wed, 08 Feb 2017 10:01:42 +0100 [thread overview]
Message-ID: <2177299.CJQXaYRB83@wuerfel> (raw)
In-Reply-To: <87wpd1h838.fsf@eliezer.anholt.net>
On Tuesday, February 7, 2017 3:52:43 PM CET Eric Anholt wrote:
> Arnd Bergmann <arnd@arndb.de> writes:
n we can take all other changes.
> >
> > For the bcm2835, try coming up with a branch that doesn't need the
> > dependency and send that separately. There are three common ways
> > to do that:
> >
> > - rebase the patches on top of the commit that introduced the header file
> > change, provided that one sits directly on top of an -rc without any
> > driver patches below it (or in the same patch)
> > - change the dts files to refer to the clk by numeric value instead of the
> > macro name, then follow up with a patch to use the name for a later
> > release
> > - defer the whole branch for the next kernel release.
>
> OK, if we can't merge the topic branch, I'll just punt on this for the
> next release. From previous topic branch merges, I thought the rule was
> "it's OK as long as you have the subsystem maintainer's ack."
I should probably explain this a bit more: We never liked those dependencies
but let them slip through in the past, as there isn't a lot of damage.
For a while we had a 'next/late' branch in which we queued up changes that
had dependencies on other branches, and then we sent that branch to Linus
once the dependencies were all merged. This works, but it's always been
annoying, so we try to avoid it completely now.
The kernel releases are frequent enough that waiting for another merge window
isn't a big deal if you plan for it in advance. Also, a lot of the header
file dependencies are completely avoidable: In some cases not using a header
leads to a better binding: e.g. most interrupt controllers just enumerate
their IRQ lines so there is no ambiguity regarding which line has which number.
For clk controllers this is often but not always the case, but often enough
you at least know what clocks are present and can give them names without
having to implement every single clk output setting in the clk controller.
Arnd
next prev parent reply other threads:[~2017-02-08 9:01 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
2017-02-07 21:12 ` Arnd Bergmann
2017-02-07 23:52 ` Eric Anholt
2017-02-08 9:01 ` Arnd Bergmann [this message]
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=2177299.CJQXaYRB83@wuerfel \
--to=arnd@arndb.de \
--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