[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121105214753.GB1254@beefymiracle.amer.corp.natinst.com>
Date: Mon, 5 Nov 2012 15:47:53 -0600
From: Josh Cartwright <josh.cartwright@...com>
To: Michal Simek <michal.simek@...inx.com>
Cc: Grant Likely <grant.likely@...retlab.ca>,
Rob Herring <rob.herring@...xeda.com>,
Russell King <linux@....linux.org.uk>,
Mike Turquette <mturquette@...com>,
John Stultz <johnstul@...ibm.com>,
Thomas Gleixner <tglx@...utronix.de>,
Alan Cox <alan@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
John Linn <John.Linn@...inx.com>,
devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-serial@...r.kernel.org
Subject: Re: [PATCH 2/8] ARM: zynq: move ttc timer code to drivers/clocksource
On Mon, Nov 05, 2012 at 12:22:55PM +0100, Michal Simek wrote:
> 2012/10/29 Josh Cartwright <josh.cartwright@...com>:
> > Suggested cleanup by Arnd Bergmann. Move the ttc timer.c code to
> > drivers/clocksource, and out of the mach-zynq directory.
> >
> > The common.h (which only held the timer declaration) was renamed to
> > xilinx_ttc.h and moved into include/linux.
> >
> > Signed-off-by: Josh Cartwright <josh.cartwright@...com>
> > Cc: Arnd Bergmann <arnd@...db.de>
> > ---
> > arch/arm/mach-zynq/Makefile | 2 +-
> > arch/arm/mach-zynq/common.c | 2 +-
> > drivers/clocksource/Makefile | 1 +
> > arch/arm/mach-zynq/timer.c => drivers/clocksource/xilinx_ttc.c | 1 -
> > arch/arm/mach-zynq/common.h => include/linux/xilinx_ttc.h | 4 ++--
> > 5 files changed, 5 insertions(+), 5 deletions(-)
> > rename arch/arm/mach-zynq/timer.c => drivers/clocksource/xilinx_ttc.c (99%)
> > rename arch/arm/mach-zynq/common.h => include/linux/xilinx_ttc.h (91%)
>
> Not going to apply this patch till there is clean way how to move all
> drivers there. Especially I don't like to add xilinx_ttc.h to
> include/linux folder.
Okay; I think it's best to defer the moving of the ttc driver from this
patchset. It is not a dependency of the clk driver support stuff.
If you agree, I can spin up a v2 of the patchset w/o this change, and
without the serial CONFIG_OF stuff. Should v2 contain the patches
you've already pulled into testing?
I'll give Rob's irqchip-like suggestion a spin and see how that works
out in parallel.
Thanks,
Josh
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists