From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-omap@vger.kernel.org
Subject: Re: [PATCH 00/10] OMAP clock updates for post 2.6.27
Date: Mon, 6 Oct 2008 16:12:25 +0100 [thread overview]
Message-ID: <20081006151225.GB27466@flint.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.0810060840430.354@utopia.booyaka.com>
On Mon, Oct 06, 2008 at 08:48:38AM -0600, Paul Walmsley wrote:
> On Thu, 2 Oct 2008, Russell King - ARM Linux wrote:
>
> > On Thu, Oct 02, 2008 at 10:37:46AM -0600, Paul Walmsley wrote:
> > > The series can be pulled from:
> > >
> > > git://git.pwsan.com/linux-2.6 omap-clock-upstream
> > >
> > > The branch is based on rmk/devel, since powerdomain and clockdomain
> > > changes are not yet in mainline.
> >
> > I assume then you haven't read the top commit on my devel branch, which
> > reads:
> >
> > DO NOT BASE YOUR TREE ON THE DEVEL BRANCH
> >
> > Merge branch 'master' into devel
> >
> > The reason is that 'devel' is a convenience merge branch of currently
> > about 25 other sub-branches for people who want to get the entire lot
> > of changes. As such, the merges found there are frequently discarded
> > and recreated.
>
> Sorry about that - thanks for the explanation.
>
> > If you want something more stable and omap related, that can be
> > arranged.
>
> That would be great. Is this the omap-all branch?
Yes - I doubt that there'll be many differences in the changes between
the two, so probably just rebasing them will be sufficient. (FYI, you
can rebase a range of commits onto another branch using 'git rebase' -
git rebase --onto target-branch first-commit^ branch-name - see the help.)
prev parent reply other threads:[~2008-10-06 15:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 16:37 [PATCH 00/10] OMAP clock updates for post 2.6.27 Paul Walmsley
2008-10-02 16:37 ` [PATCH 01/10] ARM: OMAP2: Add non-CORE DPLL rate set code and M, N programming Paul Walmsley
2008-10-02 16:37 ` [PATCH 02/10] ARM: OMAP: Fix sparse, checkpatch warnings in OMAP2/3 PRCM/PM code Paul Walmsley
2008-10-04 13:19 ` Russell King - ARM Linux
2008-10-06 14:52 ` Paul Walmsley
2008-10-06 15:09 ` Russell King - ARM Linux
2008-10-06 15:13 ` Paul Walmsley
2008-10-02 16:37 ` [PATCH 03/10] ARM: OMAP: Clock tree updates for OMAP2/3 Paul Walmsley
2008-10-02 16:37 ` [PATCH 04/10] ARM: OMAP2: Remove OMAP_PRM_REGADDR, OMAP_CM_REGADDR Paul Walmsley
2008-10-06 16:18 ` Russell King - ARM Linux
2008-10-06 23:39 ` Russell King - ARM Linux
2008-10-07 14:12 ` Paul Walmsley
2008-10-27 20:59 ` Russell King - ARM Linux
2008-11-06 13:15 ` Paul Walmsley
2008-10-07 12:54 ` Paul Walmsley
2008-10-02 16:37 ` [PATCH 05/10] ARM: OMAP2: Implement CPUfreq frequency table based on PRCM table Paul Walmsley
2008-10-02 16:37 ` [PATCH 06/10] OMAP2/3 clock: combine clkdm, clkdm_name into union in struct clk Paul Walmsley
2008-10-02 16:37 ` [PATCH 07/10] OMAP2/3 clockdomains: combine pwrdm, pwrdm_name into union in struct clockdomain Paul Walmsley
2008-10-02 16:37 ` [PATCH 08/10] OMAP2/3 clockdomains: add CM, PRM, virt_opp_clkdm clockdomains Paul Walmsley
2008-10-02 16:37 ` [PATCH 09/10] OMAP3 PRCM: add DPLL1-5 powerdomains, clockdomains; mark clocks Paul Walmsley
2008-10-02 16:37 ` [PATCH 10/10] OMAP2/3 clock: add clockdomains to all remaining clocks; remove superfluous init Paul Walmsley
2008-10-02 20:17 ` [PATCH 00/10] OMAP clock updates for post 2.6.27 Russell King - ARM Linux
2008-10-03 6:38 ` Tony Lindgren
2008-10-06 14:48 ` Paul Walmsley
2008-10-06 15:12 ` Russell King - ARM Linux [this message]
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=20081006151225.GB27466@flint.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.