linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <sugaya.taichi@socionext.com>
To: <arnd@arndb.de>
Cc: <kanematsu.shinji@socionext.com>, <masami.hiramatsu@linaro.org>,
	<daniel.lezcano@linaro.org>, <linux-kernel@vger.kernel.org>,
	<kasai.kazuhiro@socionext.com>, <jaswinder.singh@linaro.org>,
	<orito.takao@socionext.com>, <arnd.bergmann@linaro.org>,
	<linux-soc@vger.kernel.org>, <tglx@linutronix.de>,
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v2 06/15] clocksource/drivers/timer-milbeaut: Introduce timer for Milbeaut SoCs
Date: Fri, 15 Feb 2019 13:14:27 +0000	[thread overview]
Message-ID: <9b1543a25ce34affa8f0301a7505196a@SOC-EX02V.e01.socionext.com> (raw)
In-Reply-To: <CAK8P3a0G_5JmL8SMCpP4metQAG2JFeDd86t6V0K+4yxzBSEGrw@mail.gmail.com>

Hi,

> -----Original Message-----
> From: linux-arm-kernel
> [mailto:linux-arm-kernel-bounces@lists.infradead.org] On Behalf Of
> Arnd Bergmann
> Sent: Friday, February 15, 2019 6:08 PM
> To: Sugaya, Taichi/菅谷 太一
> Cc: Kanematsu, Shinji/兼松 伸次; Masami Hiramatsu; Daniel Lezcano;
> Linux Kernel Mailing List; Kasai, Kazuhiro/笠井 一洋; Jassi Brar; Orito,
> Takao/織戸 誉生; Arnd Bergmann; linux-soc@vger.kernel.org; Thomas
> Gleixner; Linux ARM
> Subject: Re: [PATCH v2 06/15] clocksource/drivers/timer-milbeaut:
> Introduce timer for Milbeaut SoCs
> 
> On Fri, Feb 15, 2019 at 3:25 AM Sugaya, Taichi
> <sugaya.taichi@socionext.com> wrote:
> > On 2019/02/15 0:18, Arnd Bergmann wrote:
> > > 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.
> >
> > Thank you for suggestion.
> > OK. I will send the series to the ML with the Acked-by/Reviewed-by tags.
> 
> One correction: please send the patches to address "soc@kernel.org"
> for inclusion.
>

I got it!

Thanks,
Sugaya Taichi

 
>       Arnd
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-02-15 13:14 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
2019-02-15  2:25         ` Sugaya, Taichi
2019-02-15  9:07           ` Arnd Bergmann
2019-02-15 13:14             ` sugaya.taichi [this message]
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=9b1543a25ce34affa8f0301a7505196a@SOC-EX02V.e01.socionext.com \
    --to=sugaya.taichi@socionext.com \
    --cc=arnd.bergmann@linaro.org \
    --cc=arnd@arndb.de \
    --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=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).