From: Arnd Bergmann <arnd@arndb.de>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Shinji Kanematsu <kanematsu.shinji@socionext.com>,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
"Sugaya, Taichi" <sugaya.taichi@socionext.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kazuhiro Kasai <kasai.kazuhiro@socionext.com>,
Jassi Brar <jaswinder.singh@linaro.org>,
Takao Orito <orito.takao@socionext.com>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
linux-soc@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 06/15] clocksource/drivers/timer-milbeaut: Introduce timer for Milbeaut SoCs
Date: Thu, 14 Feb 2019 16:18:53 +0100 [thread overview]
Message-ID: <CAK8P3a1u=u93v7FSwXMmexCvoTectdm1tDQ+g2AoB2_rTRTs=Q@mail.gmail.com> (raw)
In-Reply-To: <8f4ea33f-f176-e8d6-40fc-3286bd6a3fcc@linaro.org>
On Thu, Feb 14, 2019 at 3:44 PM Daniel Lezcano
<daniel.lezcano@linaro.org> wrote:
>
> On 13/02/2019 11:34, Sugaya, Taichi wrote:
> > Hi,
> >
> > On 2019/02/12 18:06, Daniel Lezcano wrote:
> >> On 08/02/2019 13:26, Sugaya Taichi wrote:
> >>> Add timer driver for Milbeaut SoCs series.
> >>>
> >>> The timer has two 32-bit width down counters, one of which is configured
> >>> as a clockevent device and the other is configured as a clock source.
> >>>
> >>> Signed-off-by: Sugaya Taichi <sugaya.taichi@socionext.com>
> >>
> >> Do want me to take it through my tree?
> >>
> >
> > Yes, please.
> >
> > By the way, the patch series includes other sub-system drivers, so
> > should it be splitted into each driver patch ?
>
> Well usually changes are per sub-systems but in case of first submission
> you may ask linux-soc@ team to take all the patches together with the
> acked-by tags from those subsystems maintainer.
>
> Added in Cc: Arnd@ and linux-soc@
>
> I'll wait a bit before applying the patch you clarify this.
Yes, I think merging them all together is best here.
I saw the patches fly past but did not do a complete review,
but if all other review comments are addressed, I'd suggest
sending the entire series for inclusion to linux-soc@vger.kernel.org
with the Acked-by/Reviewed-by tags from subsystem maintainers
added in.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-14 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 12:26 [PATCH v2 06/15] clocksource/drivers/timer-milbeaut: Introduce timer for Milbeaut SoCs Sugaya Taichi
2019-02-12 9:06 ` Daniel Lezcano
2019-02-13 10:34 ` Sugaya, Taichi
2019-02-14 14:44 ` Daniel Lezcano
2019-02-14 15:18 ` Arnd Bergmann [this message]
2019-02-15 2:25 ` Sugaya, Taichi
2019-02-15 9:07 ` Arnd Bergmann
2019-02-15 13:14 ` sugaya.taichi
2019-02-14 15:22 ` Daniel Lezcano
2019-02-15 2:26 ` Sugaya, Taichi
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='CAK8P3a1u=u93v7FSwXMmexCvoTectdm1tDQ+g2AoB2_rTRTs=Q@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=arnd.bergmann@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=jaswinder.singh@linaro.org \
--cc=kanematsu.shinji@socionext.com \
--cc=kasai.kazuhiro@socionext.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=orito.takao@socionext.com \
--cc=sugaya.taichi@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;
as well as URLs for NNTP newsgroup(s).