public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/6] Migrate PXA27x platforms to clock framework
Date: Tue, 30 Sep 2014 12:52:57 -0700	[thread overview]
Message-ID: <20140930195257.19023.57219@quantum> (raw)
In-Reply-To: <874mw2xoau.fsf@free.fr>

Quoting Robert Jarzmik (2014-09-20 09:13:45)
> Mike Turquette <mturquette@linaro.org> writes:
> 
> > Quoting Arnd Bergmann (2014-08-24 05:08:19)
> >> On Sunday 24 August 2014, Robert Jarzmik wrote:
> >> > > By default, I'd expect Haojian to pick up the patches and send
> >> > > us a pull request. He sent an Ack, but also didn't make it clear
> >> > > that we should pick them up.
> >> > I was thinking that they would go through the clk maintainers, hence Haojian's
> >> > ack. If they should go through arm-soc, they would need Mike's ack.
> >
> > Robert,
> >
> > I'm happy to take the patches but they will need to be rebased onto
> > clk-next and refactored to take into account Tomeu's api split[0].
> 
> Hi Mike,
> 
> I have had a look at clk-next and Tomeu's split.
> My current understanding is that Tomeu's patches don't apply on your clk-next,
> as I get conflicts.
> 
> So either I rebase my patches on top of Tomeu's tree (as this is what will drive
> most of the rebase work AFAIU), or I wait for Tomeu's tree to be merged into
> your clk-next. Is there any chance Tomeu's work ends up in your clk-next tree
> soon ?

Hi Robert,

Tomeu's stuff won't go into 3.18. I should have circled back to these
patches when that become apparent, but it got lost in the paperwork.

I can take these patches without you rebasing onto his work. Since we
have -rc7 I think there is time and these patches shouldn't wait for
another merge window. I've applied them to clk-next from a stable branch
with these six patches based on -rc1.

Hi Arnd,

I do not believe you'll need the stable branch (I tested merging it with
linux-next and there were no issues), but I've put one up anyways:

https://git.linaro.org/people/mike.turquette/linux.git clk-pxa27x

Regards,
Mike

> 
> Cheers.
> 
> -- 
> Robert

  reply	other threads:[~2014-09-30 19:52 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
2014-07-30 20:50 ` [PATCH v3 1/6] clk: add pxa clocks infrastructure Robert Jarzmik
2014-08-02 12:00   ` Haojian Zhuang
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
2014-08-23 16:05   ` Robert Jarzmik
2014-08-23 18:54     ` Arnd Bergmann
2014-08-24  9:49       ` Robert Jarzmik
2014-08-24 11:13         ` Daniel Mack
2014-08-24 12:08         ` Arnd Bergmann
2014-09-03 18:49           ` Mike Turquette
2014-09-03 19:33             ` Arnd Bergmann
2014-09-04 19:29               ` Mike Turquette
2014-09-04 21:49                 ` Arnd Bergmann
2014-09-05  4:15             ` Re : " robert.jarzmik at free.fr
2014-09-20 16:13             ` Robert Jarzmik
2014-09-30 19:52               ` Mike Turquette [this message]
2014-09-30 22:02                 ` Robert Jarzmik
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=20140930195257.19023.57219@quantum \
    --to=mturquette@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox