From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH V3] ARM: bcm281xx: Add timer driver
Date: Tue, 11 Dec 2012 13:36:11 -0700 [thread overview]
Message-ID: <50C7993B.4070201@wwwdotorg.org> (raw)
In-Reply-To: <50C785DD.8030407@broadcom.com>
On 12/11/2012 12:13 PM, Christian Daudt wrote:
> On 12-12-11 11:02 AM, Stephen Warren wrote:
>> On 12/11/2012 11:26 AM, Christian Daudt wrote:
>>> This adds support for the Broadcom timer, used in the following SoCs:
>>> BCM11130, BCM11140, BCM11351, BCM28145, BCM28155
>> For 3.9, you'll need to rebase it on top of my struct sys_timer removal
>> series, which I hope to put into linux-next ASAP after 3.8-rc1 comes out.
>
> Is there a git repo where I can look into this right now ? If so I can
> already look at what diffs will be required for this.
Sure, it's at:
git://nv-tegra.nvidia.com/user/swarren/linux-2.6 arm_timer_rework
Note that branch gets rebased, as I move it forward on to newer linux
next periodically. Once 3.8-rc1 comes out and I have a final stable
version, I'll arrange to get it into arm-soc, so it can be used as a
base for other people's patches.
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?
next prev parent reply other threads:[~2012-12-11 20:36 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 [this message]
2012-12-11 22:38 ` Arnd Bergmann
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=50C7993B.4070201@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--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