From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: Is next/cleanup of arm-soc tree stable?
Date: Mon, 14 Oct 2013 10:27:09 -0700 [thread overview]
Message-ID: <87mwmb930y.fsf@linaro.org> (raw)
In-Reply-To: <20131014161309.GG27668@S2101-09.ap.freescale.net> (Shawn Guo's message of "Tue, 15 Oct 2013 00:13:11 +0800")
Shawn Guo <shawn.guo@linaro.org> writes:
> Olof, Kevin,
>
> Per reports from linux-next folks, it seems that my imx/soc branch
> conflicts with Sebastian's clk-of-init-v2_for-3.13 quite badly. I'm
> considering to rebase my imx/soc branch on arm-soc next/cleanup branch
> to solve the conflicts. But is the branch stable, or do I have to base
> on Sebastian's clk-of-init-v2_for-3.13 branch (assume it's stable)?
Generally, the next/* branches are not stable.
It would be better if you could get a commitment from Sebastian for a
immutable branch and base directly on that.
Kevin
next prev parent reply other threads:[~2013-10-14 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 16:13 Is next/cleanup of arm-soc tree stable? Shawn Guo
2013-10-14 17:27 ` Kevin Hilman [this message]
2013-10-14 18:28 ` Sebastian Hesselbarth
2013-10-15 14:01 ` Shawn Guo
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=87mwmb930y.fsf@linaro.org \
--to=khilman@linaro.org \
--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