linux-kernel - Re: [PATCH v2 3/3] ARM: shmobile: kzm9d: Use common clock framework

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]

Date:	Wed, 9 Oct 2013 15:54:42 +0900
From:	Simon Horman <horms@...ge.net.au>
To:	Magnus Damm <magnus.damm@...il.com>
Cc:	takasi-y@....dti.ne.jp, SH-Linux <linux-sh@...r.kernel.org>,
	Ben Dooks <ben.dooks@...ethink.co.uk>,
	Shinya Kuribayashi <shinya.kuribayashi.px@...esas.com>,
	Mike Turquette <mturquette@...aro.org>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	devicetree@...r.kernel.org,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 3/3] ARM: shmobile: kzm9d: Use common clock framework

On Wed, Oct 09, 2013 at 01:59:46PM +0900, Magnus Damm wrote:
> Hi Simon,
> 
> On Wed, Oct 9, 2013 at 12:40 PM, Simon Horman <horms@...ge.net.au> wrote:
> > On Tue, Oct 08, 2013 at 02:34:03PM +0900, takasi-y@....dti.ne.jp wrote:
> >> Use common clock framework version of clock
> >>  drivers/clk/shmobile/clk-emev2.c
> >> instead of sh-clkfwk version
> >>  arch/arm/mach-shmobile/clock-emev2.c
> >> when it is configured as a part of multi-platform.
> >>
> >> Signed-off-by: Takashi Yoshii <takasi-y@....dti.ne.jp>
> >
> > Thanks.
> >
> > I plan to add this patch to a new topic branch,
> > topic/emev2-common-clock, in the renesas tree and
> > queue it up from there for inclusion in mainline
> > if/when the first patch of this series is accepted
> > by Mike Turquette.
> 
> Thanks for picking up patches, Simon.
> 
> I think you can simply merge this patch after the following series:
> 
> [PATCH 00/05] ARM: shmobile: KZM9D Multiplatform update

This is already queued up.

> There are no build time dependencies on patch 1 and 2 so this patch
> can be merged independently. Regarding run-time operation, the
> multiplatform series above makes KZM9D DT reference only build for
> multiplatform, and in such case CCF is required.
> 
> So if you want to keep KZM9D DT reference working until Mike Turquette
> accepts the CCF bits, then I recommend you to wait with "[PATCH 00/05]
> ARM: shmobile: KZM9D Multiplatform update" until all EMEV2 CCF bits
> have been merged.
> 
> Another way is to merge "[PATCH 00/05] ARM: shmobile: KZM9D
> Multiplatform update" before the EMEV2 CCF bits, but if so you may as
> well merge this patch as well IMO. This
> multiplatform-update-series-merge-before-CCF plan will result in
> untestable KZM9D DT reference until EMEV2 CCF is merged. Either way is
> fine with me.

I am mainly concerned that the bindings may change before
they are finally merged. And I thought it would be nice to avoid
having to fix up the usage of the bindings if they change.

But I'm happy to just queue-up patches 2 and 3 of this series
now if you prefer.
--
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/