From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Noam Camus <noamca@mellanox.com>,
LKML <linux-kernel@vger.kernel.org>,
<Alexey.Brodkin@synopsys.com>, <tglx@linutronix.de>,
<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH v4 8/8] clocksource: import ARC timer driver
Date: Tue, 15 Nov 2016 09:16:44 -0800 [thread overview]
Message-ID: <de38a2d1-d868-77fe-70ae-7ca7b3c8b975@synopsys.com> (raw)
In-Reply-To: <9c03641f-b6a4-9e3b-53ee-03788771dbeb@linaro.org>
On 11/15/2016 02:30 AM, Daniel Lezcano wrote:
>> Thx Daniel. So I suppose for 4.10, I will get these merged,
>> > including the
>> > driver/clocksource bits. OK ?
> Hi Vineet,
>
> I just want to clarify. Do you want the entire series to go through my
> tree ? Or through your tree ?
I'd prefer my tree ! FWIW per our last agreement, I already pushed it to my
for-next :-)
-Vineet
next prev parent reply other threads:[~2016-11-15 17:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 21:38 [PATCH v4 0/8] Move ARC timer code into drivers/clocksource/ Vineet Gupta
2016-11-11 21:38 ` [PATCH v4 1/8] ARC: timer: gfrc, rtc: deuglify big endian code Vineet Gupta
2016-11-11 21:38 ` [PATCH v4 2/8] ARC: timer: gfrc, rtc: Read BCR to detect whether hardware exists Vineet Gupta
2016-11-11 21:38 ` [PATCH v4 3/8] ARC: time: move time_init() out of the driver Vineet Gupta
2016-11-11 21:38 ` [PATCH v4 4/8] ARC: timer: Build gfrc, rtc under same option (64-bit timers) Vineet Gupta
2016-11-11 21:38 ` [PATCH v4 5/8] ARC: breakout aux handling into a separate header Vineet Gupta
2016-11-11 21:38 ` [PATCH v4 6/8] ARC: move mcip.h into include/soc and adjust the includes Vineet Gupta
2016-11-11 21:38 ` [PATCH v4 7/8] ARC: breakout timer include code into separate header Vineet Gupta
2016-11-11 21:38 ` [PATCH v4 8/8] clocksource: import ARC timer driver Vineet Gupta
2016-11-11 23:11 ` Daniel Lezcano
2016-11-12 0:53 ` Vineet Gupta
[not found] ` <CAKnoXLzY7Qxw39R029cprqzy4WvKXYf5PReutORO+JyMvaxeqA@mail.gmail.com>
2016-11-15 10:30 ` Daniel Lezcano
2016-11-15 17:16 ` Vineet Gupta [this message]
2016-11-15 17:23 ` Daniel Lezcano
2016-11-15 17:27 ` Vineet Gupta
[not found] ` <DB6PR0501MB2518CBABEBEB7499F0D023A0AABF0@DB6PR0501MB2518.eurprd05.prod.outlook.com>
2016-11-15 17:49 ` Daniel Lezcano
[not found] ` <DB6PR0501MB25183F3E7B3B5D224F646F79AABF0@DB6PR0501MB2518.eurprd05.prod.outlook.com>
2016-11-15 19:29 ` Daniel Lezcano
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=de38a2d1-d868-77fe-70ae-7ca7b3c8b975@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=noamca@mellanox.com \
--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®