All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/6] Migrate PXA27x platforms to clock framework
Date: Thu, 4 Sep 2014 23:49:30 +0200	[thread overview]
Message-ID: <201409042349.31210.arnd@arndb.de> (raw)
In-Reply-To: <20140904192943.11368.83896@quantum>

On Thursday 04 September 2014, Mike Turquette wrote:
> 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.

Ok, I see. We might not pull it in right away, because it's possible that there
are no actual conflicts and we don't need them, but it's definitely good
if your branch is ready in case we do.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Mike Turquette <mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Robert Jarzmik <robert.jarzmik-GANU6spQydw@public.gmane.org>,
	Russell King - ARM Linux
	<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	Daniel Mack <zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Eric Miao <eric.y.miao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Haojian Zhuang
	<haojian.zhuang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org
Subject: Re: [PATCH v3 0/6] Migrate PXA27x platforms to clock framework
Date: Thu, 4 Sep 2014 23:49:30 +0200	[thread overview]
Message-ID: <201409042349.31210.arnd@arndb.de> (raw)
In-Reply-To: <20140904192943.11368.83896@quantum>

On Thursday 04 September 2014, Mike Turquette wrote:
> 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-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
> > 
> > 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.

Ok, I see. We might not pull it in right away, because it's possible that there
are no actual conflicts and we don't need them, but it's definitely good
if your branch is ready in case we do.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-09-04 21:49 UTC|newest]

Thread overview: 48+ 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
2014-07-30 20:50 ` Robert Jarzmik
2014-07-30 20:50 ` [PATCH v3 1/6] clk: add pxa clocks infrastructure Robert Jarzmik
2014-07-30 20:50   ` Robert Jarzmik
2014-08-02 12:00   ` Haojian Zhuang
2014-08-02 12:00     ` Haojian Zhuang
2014-08-02 16:46     ` Robert Jarzmik
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   ` 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   ` Robert Jarzmik
2014-07-30 20:51 ` [PATCH v3 4/6] clk: add pxa27x clock drivers Robert Jarzmik
2014-07-30 20:51   ` 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   ` Robert Jarzmik
2014-07-30 20:51 ` [PATCH v3 6/6] arm: pxa: Transition pxa27x to clk framework Robert Jarzmik
2014-07-30 20:51   ` Robert Jarzmik
2014-08-02 12:27 ` [PATCH v3 0/6] Migrate PXA27x platforms to clock framework Haojian Zhuang
2014-08-02 12:27   ` Haojian Zhuang
2014-08-23 16:05   ` Robert Jarzmik
2014-08-23 16:05     ` Robert Jarzmik
2014-08-23 18:54     ` Arnd Bergmann
2014-08-23 18:54       ` Arnd Bergmann
2014-08-24  9:49       ` Robert Jarzmik
2014-08-24  9:49         ` Robert Jarzmik
2014-08-24 11:13         ` Daniel Mack
2014-08-24 11:13           ` Daniel Mack
2014-08-24 12:08         ` Arnd Bergmann
2014-08-24 12:08           ` Arnd Bergmann
2014-09-03 18:49           ` Mike Turquette
2014-09-03 18:49             ` Mike Turquette
2014-09-03 19:33             ` Arnd Bergmann
2014-09-03 19:33               ` Arnd Bergmann
2014-09-04 19:29               ` Mike Turquette
2014-09-04 19:29                 ` Mike Turquette
2014-09-04 21:49                 ` Arnd Bergmann [this message]
2014-09-04 21:49                   ` Arnd Bergmann
2014-09-05  4:15             ` Re : " robert.jarzmik at free.fr
2014-09-05  4:15               ` robert.jarzmik-GANU6spQydw
2014-09-20 16:13             ` Robert Jarzmik
2014-09-20 16:13               ` Robert Jarzmik
2014-09-30 19:52               ` Mike Turquette
2014-09-30 19:52                 ` Mike Turquette
2014-09-30 22:02                 ` Robert Jarzmik
2014-09-30 22:02                   ` Robert Jarzmik
2014-09-30 22:10                   ` Mike Turquette
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=201409042349.31210.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 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.