From: mmayer@broadcom•com (Markus Mayer)
To: linux-arm-kernel@lists•infradead.org
Subject: Branches next/soc and for-next
Date: Thu, 29 Nov 2012 12:02:09 -0800 [thread overview]
Message-ID: <50B7BF41.7060807@broadcom.com> (raw)
Hi Arnd and Olof,
Following a short discussion with Pawel regarding a build breakage in
next/soc (see
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/thread.html#135208),
I would like to ask you for some clarification as to the differences
between the branches next/soc and for-next and what that means for
development.
If I understand correctly, next/soc is being used to integrate SoC work
from various board- or vendor-specific branches. for-next, in turn,
integrates next/soc with driver branches and other non-SoC related
branches. Is this somewhat accurate? -- What happens to code in
for-next? Is that what eventually gets pulled into mainline?
As I mentioned in my discussion with Pawel, next/soc currently doesn't
build for vexpress and, since vexpress is multiplatform-enabled, no
other multiplatform target will build, either. The reason for this,
Pawel explained, was that he was asked to split his patch, so it could
be applied to different branches, depending on the subsystem area his
changes were made in. As a result, a file needed for compilation
(arch/mach-vexpress/reset.c) is missing in next/soc.
How are such build errors generally addressed? How long does it usually
take? And, lastly, which branch would you recommend to use for
development to generate patches relative to arm-soc?
Thanks for your help.
Regards,
-Markus
next reply other threads:[~2012-11-29 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 20:02 Markus Mayer [this message]
2012-11-29 21:45 ` Branches next/soc and for-next Arnd Bergmann
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=50B7BF41.7060807@broadcom.com \
--to=mmayer@broadcom$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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