From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3] ARM: bcm281xx: Add timer driver
Date: Tue, 11 Dec 2012 22:38:19 +0000 [thread overview]
Message-ID: <201212112238.19528.arnd@arndb.de> (raw)
In-Reply-To: <50C7993B.4070201@wwwdotorg.org>
On Tuesday 11 December 2012, Stephen Warren wrote:
> Olof, Arnd, that brings me to the question of:
>
> Should I:
>
> a) Add that branch into linux-next (e.g. via the Tegra tree's for-next)
> right after v3.8-rc1, let is sit there for a week or two (to allow
> rebasing to squash in any fixes that show up as being needed), and then
> send a pull request to arm-soc as a stable branch,
>
> or:
>
> b) Send a pull request to arm-soc right after 3.8-rc1, and let you do
> any rebasing/squashing needed, before declaring it stable say around
> 3.8-rc2 or 3.8-rc3?
I think either way works fine. The first one is less work for us though ;-)
Arnd
next prev parent reply other threads:[~2012-12-11 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 18:26 [PATCH V3] ARM: bcm281xx: Add timer driver Christian Daudt
2012-12-11 19:02 ` Stephen Warren
2012-12-11 19:13 ` Christian Daudt
2012-12-11 19:22 ` Olof Johansson
2012-12-11 20:36 ` Stephen Warren
2012-12-11 22:38 ` Arnd Bergmann [this message]
2012-12-11 22:42 ` 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=201212112238.19528.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;
as well as URLs for NNTP newsgroup(s).