public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
	Mike Turquette <mturquette@linaro.org>,
	linux-kernel@vger.kernel.org,
	Russell King <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 00/10] clk: mvebu: restructure SoC clock drivers
Date: Mon, 20 May 2013 20:56:16 +0200	[thread overview]
Message-ID: <519A71D0.7090103@free-electrons.com> (raw)
In-Reply-To: <20130520201549.475e50d0@skate>

On 05/20/2013 08:15 PM, Thomas Petazzoni wrote:
> Dear Jason Cooper,
> 
> On Mon, 20 May 2013 13:58:27 -0400, Jason Cooper wrote:
> 
>>> I've tested on Armada 370 DB (after reverting the ARM core patch
>>> that prevents this platform from booting) and the Armada XP DB.
>>> Both boards boot fine, and detect PCIe devices as they should.
>>>
>>> There is some conflict between this set of commits and the two
>>> commits that modify the PCIe clocks in my PCIe series. I've pushed
>>> a branch at
>>> https://github.com/MISL-EBU-System-SW/mainline-public/tree/marvell-pcie-v10-and-seb-clks
>>> which has the mvebu PCIe stuff + Sebastian patches on top of it,
>>> with the conflicts resolved. The tricky thing is that since
>>> Sebastian is adding new clock files, and then removing the old
>>> ones, it's pretty easy to "loose" the changes the two PCIe clock
>>> patches are doing. The branch above works on Armada 370/XP, so you
>>> can compare the clock files if needed.
>>
>> hmm, in my haste yesterday, I did this in the opposite order (clk,
>> then pcie on top).  I'm going to reshuffle them because I don't want
>> pcie depending on and waiting for this clock series to be ready :)
> 
> Ok. Either way is fine with me, but it's true that chronologically, the
> PCIe stuff has been around for way more time than the clk
> restructure patches.
> 
>> The good news is everything (except kirkwood-pcie, ran out of time)
>> made it through linux-next!  Also, kisskb is now building
>> mvebu_defconfig in addition to all the other ones.
> 
> Ok. Gregory can give more details, but I believe we are also building
> daily linux-next and Linus master for the mvebu_defconfig.

Indeed every day we build linux-next for the mvebu_defconfig and for
multi_v7_defconfig (as mvebu is part of it). You can see the status here:

http://jenkins.free-electrons.com/job/linux-next/

However we don't build Linus master but we could add it.


> 
> Best regards,
> 
> Thomas
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-05-20 18:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-11  1:08 [PATCH 00/10] clk: mvebu: restructure SoC clock drivers Sebastian Hesselbarth
2013-05-11  1:08 ` [PATCH 01/10] clk: mvebu: introduce per-clock-gate flags Sebastian Hesselbarth
2013-05-28 15:44   ` Jason Cooper
2013-05-11  1:08 ` [PATCH 02/10] clk: mvebu: add common clock functions for core clk and clk gating Sebastian Hesselbarth
2013-05-11  1:08 ` [PATCH 03/10] clk: mvebu: add Dove SoC-centric clock init Sebastian Hesselbarth
2013-05-11  1:08 ` [PATCH 04/10] clk: mvebu: add Kirkwood " Sebastian Hesselbarth
2013-05-11  1:08 ` [PATCH 05/10] clk: mvebu: add Armada 370 " Sebastian Hesselbarth
2013-05-28 15:46   ` Jason Cooper
2013-05-11  1:08 ` [PATCH 06/10] clk: mvebu: add Armada XP " Sebastian Hesselbarth
2013-05-28 15:48   ` Jason Cooper
2013-05-11  1:08 ` [PATCH 07/10] ARM: dove: move DT boards to " Sebastian Hesselbarth
2013-05-11  1:08 ` [PATCH 08/10] ARM: kirkwood: " Sebastian Hesselbarth
2013-05-11  1:08 ` [PATCH 09/10] ARM: mvebu: " Sebastian Hesselbarth
2013-05-11  1:08 ` [PATCH 10/10] clk: mvebu: desintegrate obsolete file Sebastian Hesselbarth
2013-05-16 16:46 ` [PATCH 00/10] clk: mvebu: restructure SoC clock drivers Thomas Petazzoni
2013-05-20 17:58   ` Jason Cooper
2013-05-20 18:15     ` Thomas Petazzoni
2013-05-20 18:56       ` Gregory CLEMENT [this message]
2013-05-19 20:13 ` Jason Cooper
2013-05-28 15:40 ` Jason Cooper
2013-05-28 15:53   ` Thomas Petazzoni
2013-05-28 15:58     ` Sebastian Hesselbarth
2013-05-28 16:54     ` Jason Cooper
2013-05-28 20:01       ` Sebastian Hesselbarth
2013-05-28 20:03         ` Jason Cooper
2013-05-29 19:02 ` Mike Turquette
2013-05-29 19:05   ` Sebastian Hesselbarth
2013-05-29 19:17     ` Jason Cooper

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=519A71D0.7090103@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --cc=andrew@lunn.ch \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mturquette@linaro.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=thomas.petazzoni@free-electrons.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