[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130207.220504.79003148683176035.hdoyu@nvidia.com>
Date: Thu, 7 Feb 2013 21:05:04 +0100
From: Hiroshi Doyu <hdoyu@...dia.com>
To: "swarren@...dotorg.org" <swarren@...dotorg.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
CC: "robherring2@...il.com" <robherring2@...il.com>,
"arm@...nel.org" <arm@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
"johnstul@...ibm.com" <johnstul@...ibm.com>
Subject: Re: [PATCH 4/4] clocksource: tegra20: use the device_node pointer
passed to init
Stephen Warren <swarren@...dotorg.org> wrote @ Thu, 7 Feb 2013 20:39:40 +0100:
> On 02/07/2013 12:09 PM, Rob Herring wrote:
> > From: Rob Herring <rob.herring@...xeda.com>
> >
> > We've already matched the node, so use the node pointer passed in. The rtc
> > init was intermingled with the timer init, so split this out to a separate
> > init function.
>
> The series,
> Reviewed-by: Stephen Warren <swarren@...dia.com>
>
> Patches 1,4:
> Tested-by: Stephen Warren <swarren@...dia.com>
>
> One thing I wonder re: patch 4 - I know someone (I think Hiroshi, now
> CC'd) planned to refactor drivers/clocksource/tegra20_timer.c to enhance
> it for Tegra114. I'd like to check with him that the refactoring in this
> patch won't impede that at all.
Actually this covers RTC part. I'll rework mine for the rest on the
top of this.
--
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/
Powered by blists - more mailing lists