From: "Sugaya, Taichi" <sugaya.taichi@socionext.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Cc: Takao Orito <orito.takao@socionext.com>,
Kazuhiro Kasai <kasai.kazuhiro@socionext.com>,
Shinji Kanematsu <kanematsu.shinji@socionext.com>,
Jassi Brar <jaswinder.singh@linaro.org>,
Masami Hiramatsu <masami.hiramatsu@linaro.org>
Subject: Re: [PATCH v2 0/3] Bugfix and cleanup the timer driver for Milbeaut M10V
Date: Fri, 12 Apr 2019 21:34:43 +0900 [thread overview]
Message-ID: <5a58fdda-ada9-09bb-6d82-2e636f47df08@socionext.com> (raw)
In-Reply-To: <2b6c5bad-485e-657d-e5fe-17fb6281041e@linaro.org>
Hi,
On 2019/04/12 20:09, Daniel Lezcano wrote:
> On 12/04/2019 09:36, Sugaya Taichi wrote:
>> This series fixes a bug and cleanup code about timer driver for
>> Milbeaut M10V.
>> Since it is difficult to separate, it is integrated into a series.
>>
>> Changes from v1:
>> -Add "Fixes" tag.
>>
>> Sugaya Taichi (3):
>> clocksource/drivers/timer-milbeaut: Fix to enable one-shot timer
>> clocksource/drivers/timer-milbeaut: Add shutdown function
>> clocksource/drivers/timer-milbeaut: Cleanup common register accesses
>>
>> drivers/clocksource/timer-milbeaut.c | 66 +++++++++++++++++++++++++-----------
>> 1 file changed, 47 insertions(+), 19 deletions(-)
>
> Series applied for 5.2
>
> Thanks
>
> -- Daniel
>
>
Thank you!
prev parent reply other threads:[~2019-04-12 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 7:36 Sugaya Taichi
2019-04-12 7:36 ` [PATCH v2 1/3] clocksource/drivers/timer-milbeaut: Fix to enable one-shot timer Sugaya Taichi
2019-04-12 7:36 ` [PATCH v2 2/3] clocksource/drivers/timer-milbeaut: Add shutdown function Sugaya Taichi
2019-04-12 7:36 ` [PATCH v2 3/3] clocksource/drivers/timer-milbeaut: Cleanup common register accesses Sugaya Taichi
2019-04-12 11:09 ` [PATCH v2 0/3] Bugfix and cleanup the timer driver for Milbeaut M10V Daniel Lezcano
2019-04-12 12:34 ` Sugaya, Taichi [this message]
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=5a58fdda-ada9-09bb-6d82-2e636f47df08@socionext.com \
--to=sugaya.taichi@socionext.com \
--cc=daniel.lezcano@linaro.org \
--cc=jaswinder.singh@linaro.org \
--cc=kanematsu.shinji@socionext.com \
--cc=kasai.kazuhiro@socionext.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=orito.takao@socionext.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®