From: Mike Turquette <mturquette@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Daniel Mack <zonque@gmail.com>,
arm@kernel.org, olof@lixom.net, Eric Miao <eric.y.miao@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/6] Migrate PXA27x platforms to clock framework
Date: Thu, 04 Sep 2014 12:29:43 -0700 [thread overview]
Message-ID: <20140904192943.11368.83896@quantum> (raw)
In-Reply-To: <3966110.RPrxdc8FBm@wuerfel>
Quoting Arnd Bergmann (2014-09-03 12:33:31)
> On Wednesday 03 September 2014 11:49:56 Mike Turquette wrote:
> > > Right, makes sense. We have in the past done it either way for other
> > > platforms. When merging the patches through the clk subsystem, it still
> > > makes sense to let us know of those plans and ask for an Ack from
> > > the arm-soc maintainers, to be sure we can plan ahead in case there
> > > are other (conflicting) patch sets that are sent through arm-soc.
> >
> > Do I have your Ack for the arch/arm patches?
> >
> > [0] https://lkml.kernel.org/r/<1409758148-20104-1-git-send-email-tomeu.vizoso@collabora.com>
>
> I have no objection to the change, but we might need to be careful in
> case we get a lot of conflicts.
>
> How about making it a shared branch that you plan to send upstream
> but that we can also include in arm-soc to avoid conflicts if necessary?
Sounds good. I'll probably need to perform a bit of surgery on my tree
and rebase it in order to have the minimum set of patches that get
pulled into arm-soc.
Regards,
Mike
>
> Arnd
next prev parent reply other threads:[~2014-09-04 19:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 20:50 [PATCH v3 0/6] Migrate PXA27x platforms to clock framework Robert Jarzmik
[not found] ` <1406753464-15000-1-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2014-07-30 20:50 ` [PATCH v3 1/6] clk: add pxa clocks infrastructure Robert Jarzmik
[not found] ` <1406753464-15000-2-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2014-08-02 12:00 ` Haojian Zhuang
[not found] ` <CAN1soZyST84DNvK=zyj6EhOt0fswZ4SvOmMnWiCZsYmapxkhOg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-02 16:46 ` Robert Jarzmik
2014-07-30 20:51 ` [PATCH v3 2/6] clk: dts: document pxa clock binding Robert Jarzmik
2014-07-30 20:51 ` [PATCH v3 3/6] arm: pxa: add clock pll selection bits Robert Jarzmik
2014-07-30 20:51 ` [PATCH v3 4/6] clk: add pxa27x clock drivers Robert Jarzmik
2014-07-30 20:51 ` [PATCH v3 5/6] dts: add devicetree bindings for pxa27x clocks Robert Jarzmik
2014-07-30 20:51 ` [PATCH v3 6/6] arm: pxa: Transition pxa27x to clk framework Robert Jarzmik
2014-08-02 12:27 ` [PATCH v3 0/6] Migrate PXA27x platforms to clock framework Haojian Zhuang
[not found] ` <CAN1soZwDDwiLuVkT7kRJX-wy-UmyDj-2yiReGrpBrTOJkKpuSA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-23 16:05 ` Robert Jarzmik
[not found] ` <87ha1342ei.fsf-GANU6spQydw@public.gmane.org>
2014-08-23 18:54 ` Arnd Bergmann
2014-08-24 9:49 ` Robert Jarzmik
[not found] ` <87d2bq43pc.fsf-GANU6spQydw@public.gmane.org>
2014-08-24 11:13 ` Daniel Mack
2014-08-24 12:08 ` Arnd Bergmann
[not found] ` <201408241408.19861.arnd-r2nGTMty4D4@public.gmane.org>
2014-09-03 18:49 ` Mike Turquette
2014-09-03 19:33 ` Arnd Bergmann
2014-09-04 19:29 ` Mike Turquette [this message]
2014-09-04 21:49 ` Arnd Bergmann
2014-09-05 4:15 ` Re : " robert.jarzmik-GANU6spQydw
2014-09-20 16:13 ` Robert Jarzmik
[not found] ` <874mw2xoau.fsf-GANU6spQydw@public.gmane.org>
2014-09-30 19:52 ` Mike Turquette
2014-09-30 22:02 ` Robert Jarzmik
[not found] ` <87iok4bwcj.fsf-GANU6spQydw@public.gmane.org>
2014-09-30 22:10 ` Mike Turquette
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=20140904192943.11368.83896@quantum \
--to=mturquette@linaro.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=robert.jarzmik@free.fr \
--cc=zonque@gmail.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 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).