From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] ARC: Use clockevents_config_and_register over clockevents_register_device
Date: Fri, 27 Sep 2013 10:52:03 +0200 [thread overview]
Message-ID: <20130927085203.GM16106@pengutronix.de> (raw)
In-Reply-To: <C2D7FE5348E1B147BCA15975FBA2307514EB8B@IN01WEMBXA.internal.synopsys.com>
Hello,
On Fri, Sep 27, 2013 at 08:26:58AM +0000, Vineet Gupta wrote:
> On 09/27/2013 01:47 PM, Uwe Kleine-König wrote:
> > On Thu, Sep 26, 2013 at 12:01:49PM +0000, Vineet Gupta wrote:
> >> On 09/25/2013 02:35 AM, Uwe Kleine-König wrote:
> >>> clockevents_config_and_register is more clever and correct than doing it
> >>> by hand; so use it.
> >>>
> >>> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> >> Acked-by: Vineet Gupta <vgupta@synopsys.com>
> > Thanks for the ack, but I expected that it will be you who takes that
> > patch. Am I wrong? Who will take it instead?
>
> Well that really depends - if there's a series of such fixes, people generally
> route it thru mm or some such.
I still have a few such fixes in the queue, but as they are all
independant of each other I think it would be best if you took it.
Thanks
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-09-27 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 21:05 Uwe Kleine-König
2013-09-26 12:01 ` Vineet Gupta
2013-09-27 8:17 ` Uwe Kleine-König
2013-09-27 8:26 ` Vineet Gupta
2013-09-27 8:52 ` Uwe Kleine-König [this message]
2013-09-27 9:00 ` Vineet Gupta
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=20130927085203.GM16106@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=Vineet.Gupta1@synopsys.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®