linux-kernel - Re: [PATCH 00/10] clk: mvebu: restructure SoC clock drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130528175343.77c6353d@skate>
Date:	Tue, 28 May 2013 17:53:43 +0200
From:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
To:	Jason Cooper <jason@...edaemon.net>
Cc:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	Andrew Lunn <andrew@...n.ch>,
	Russell King <linux@....linux.org.uk>,
	linux-kernel@...r.kernel.org,
	Gregory Clement <gregory.clement@...e-electrons.com>,
	Mike Turquette <mturquette@...aro.org>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 00/10] clk: mvebu: restructure SoC clock drivers

Dear Jason Cooper,

On Tue, 28 May 2013 11:40:47 -0400, Jason Cooper wrote:

> In order to avoid losing changes between this series and mvebu/pcie,
> I've rebased this series on top of mvebu/pcie and incorporated the
> correct conflict resolution into this series.  See below...

Thanks!

> I'm posting the revised version as replies to patches 1, 5 and 6. Please
> let me know if I messed it up.  I'd like to send the PR for these
> shortly.

I had a quick look, and it looks good to me. Let me know to which
branch you've pushed this, and the merge order to follow to "rebuild"
something that works, and I'll try to find some time to test it for
real on hardware.

Thanks again!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/