From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: BCM5301X: SoC changes for v3.19
Date: Fri, 21 Nov 2014 12:42:12 +0100 [thread overview]
Message-ID: <2449000.zVL0dbsxYm@wuerfel> (raw)
In-Reply-To: <546E52E9.3040301@hauke-m.de>
On Thursday 20 November 2014 21:45:29 Hauke Mehrtens wrote:
> On 11/20/2014 10:27 AM, Arnd Bergmann wrote:
> > - The pull request is based on -rc4, but I see no strong reason why you did
> > that. It helps us a lot of all pull requests in a branch are based off
> > the same -rc, so please have them based on -rc1 by default or explain why
> > you picked something else in the tag description.
>
> I just thought that I should base it on a recent -rc, so I took -rc4, I
> can rebase it on rc1 if you like, I do not depend on any new stuff.
No, you should base on the oldest -rc that works for you to avoid backmerges.
When I start the next/soc branch from -rc1 and I pull in a branch that
is based on -rc4, 'git request-pull' can no longer figure out what the
base changeset was and I have to manually edit the pull request.
> > If you want, I can just cherry-pick the two patches from your branch into
> > the next/soc branch so you don't have to rebase it this time.
>
> That would be nice.
>
I've cherry-picked the first one, but the "BCM5301X: select GPIOLIB as
optional" change no longer applies: as part of Scott's "ARM: mach-bcm:
Consolidate currently supported IPROC SoCs", bcm5301x now selects
ARCH_IPROC, which already uses ARCH_REQUIRE_GPIOLIB.
Let me know if that is a problem.
Arnd
prev parent reply other threads:[~2014-11-21 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 23:16 [GIT PULL] ARM: BCM5301X: SoC changes for v3.19 Hauke Mehrtens
2014-11-20 9:27 ` Arnd Bergmann
2014-11-20 20:45 ` Hauke Mehrtens
2014-11-20 20:48 ` Florian Fainelli
2014-11-21 11:50 ` Arnd Bergmann
2014-11-21 11:42 ` Arnd Bergmann [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=2449000.zVL0dbsxYm@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;
as well as URLs for NNTP newsgroup(s).