From: mturquette@ti.com (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] clk: ux500: Make mtu driver use apb_pclock
Date: Mon, 12 Nov 2012 10:36:15 -0800 [thread overview]
Message-ID: <20121112183615.17970.20162@nucleus> (raw)
In-Reply-To: <CACRpkdbGnvywcQWRN9v_=1nkmaqgJK92Zs1S5HSLgppa49bQqw@mail.gmail.com>
Quoting Linus Walleij (2012-11-11 10:47:46)
> On Sat, Nov 10, 2012 at 2:24 AM, Mike Turquette <mturquette@linaro.org> wrote:
> > Quoting Linus Walleij (2012-10-24 10:25:26)
> >> On Wed, Oct 24, 2012 at 2:13 PM, Ulf Hansson <ulf.hansson@stericsson.com> wrote:
> >>
> >> > From: Ulf Hansson <ulf.hansson@linaro.org>
> >> >
> >> > The apb clock was before the "common" clock driver for ux500 was merged,
> >> > handled internally by the clock driver. Now this clock needs to be managed
> >> > from the mtu driver as a separate clock.
> >> >
> >> > This patches is based in 3.7 rc2.
> >> >
> >> > It is important the "ARM nomadik patch" is merged together with the
> >> > clock patch to not break boot. Therefore I suggest this series to go
> >> > through Mike Turquettes clock tree.
> >>
> >> OK go ahead:
> >> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> >
> > I've taken these into clk-next. While the patches are trivial I'd still
> > prefer a changelog in the future. For instance, it would be nice to
> > explain why removing the block comment is OK in the first patch.
>
> So there may be some collision in linux-next due to this,
> because I've moved the nomadik timer to
> drivers/clksrc and deleted the entire plat-nomadik
> directory.
>
> I don't know quite how ingenious git is in detecting
> patches on moved files, but if it's causing trouble
> I think it's better if you could ACK them and we
> could reubmit them to ARM SoC on the multiplatform
> branch. i.e. this one:
> http://git.kernel.org/?p=linux/kernel/git/arm/arm-soc.git;a=shortlog;h=refs/heads/next/multiplatform
>
Those patches have my ACK. Do you want to wait to see if something goes
boom or would you rather I drop them from clk-next preemptively?
Regards,
Mike
> Yours,
> Linus Walleij
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2012-11-12 18:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 12:13 [PATCH 0/2] clk: ux500: Make mtu driver use apb_pclock Ulf Hansson
2012-10-24 12:13 ` [PATCH 1/2] clk: ux500: Register mtu apb_pclocks Ulf Hansson
2012-10-24 12:13 ` [PATCH 2/2] ARM: plat-nomadik: Use apb_pclock in mtu driver Ulf Hansson
2012-10-24 17:25 ` [PATCH 0/2] clk: ux500: Make mtu driver use apb_pclock Linus Walleij
2012-11-10 1:24 ` Mike Turquette
2012-11-11 18:47 ` Linus Walleij
2012-11-12 18:36 ` Mike Turquette [this message]
2012-11-15 10:29 ` Linus Walleij
2012-11-15 12:21 ` Arnd Bergmann
2012-11-15 13:29 ` Linus Walleij
2012-11-15 18:54 ` Mike Turquette
2012-11-16 9:17 ` Ulf Hansson
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=20121112183615.17970.20162@nucleus \
--to=mturquette@ti.com \
--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 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.