From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ux500 <mach/id.h> removal
Date: Wed, 30 Jan 2013 23:15:22 +0000 [thread overview]
Message-ID: <201301302315.22357.arnd@arndb.de> (raw)
In-Reply-To: <CACRpkdYmTTgpnAOoNM3RJiF_oADgbuGK-vw6JF8J9rPAttA5PQ@mail.gmail.com>
On Wednesday 30 January 2013, Linus Walleij wrote:
> On Wed, Jan 30, 2013 at 1:12 AM, Olof Johansson <olof@lixom.net> wrote:
> > [Me]
> >> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-stericsson.git
> >> tags/ux500-no-idh
> >
> > Pulled in.
> >
> > This has a somewhat annoying (but trivial) conflict against your own
> > code (the cpufreq driver changes).
>
> Arnd always told me to split stuff cleanly on branches, which of course
> leads to conflicts like that, but I thought he wanted them, rather than
> huge accumulated patch sets built on to of each othere ... a bit hard to
> do the right thing here, what would have been the right way?
>
> Does it help if I base stuff off ARM SoC tree branches, and which
> ones can be relied upon in that case?
Not sure if it applies here, but in a lot of cases, one can extract the
parts that do conflict and put those patches first in the series, and
merge them together before the pull request.
The classic example of this is two independent features A and B that
both contain some cleanup. By moving the cleanup first, you can merge
the cleanup-A patches with the cleanup-B patches and submit them as one
branch, and then have feature A on top of cleanup-A merge cleanly with
both feature-B (because there are no conflicts) and with cleanup-A-B
(because cleanup-A-B has already resolved the conflict).
Unrelated to this: The mach/id.h removal seems to have caused a few
build errors in the for-next tree with u8500_defconfig. Can you have
a look at what went wrong there?
Arnd
next prev parent reply other threads:[~2013-01-30 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 18:06 [GIT PULL] ux500 <mach/id.h> removal Linus Walleij
2013-01-30 0:12 ` Olof Johansson
2013-01-30 9:39 ` Linus Walleij
2013-01-30 23:15 ` Arnd Bergmann [this message]
2013-01-31 14:40 ` Linus Walleij
2013-02-05 22:22 ` Olof Johansson
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=201301302315.22357.arnd@arndb.de \
--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