From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arm-soc <arm@kernel.org>, linux-omap <linux-omap@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL 2/6] omap timer changes for v4.17
Date: Wed, 7 Mar 2018 07:28:42 -0800 [thread overview]
Message-ID: <20180307152842.GH5799@atomide.com> (raw)
In-Reply-To: <CAK8P3a0YwGtE+UkA6+rQ_FQsGO5paL9ub_=oOq_SE3xPUiH1ww@mail.gmail.com>
* Arnd Bergmann <arnd@arndb.de> [180307 15:22]:
> On Mon, Mar 5, 2018 at 7:11 PM, Tony Lindgren <tony@atomide.com> wrote:
> > From: "Tony Lindgren" <tony@atomide.com>
> >
> > The following changes since commit 2fdc82776ac2ac49c5ee666d834718ac36420e49:
> >
> > Merge branch 'omap-for-v.16/dmtimer-fix' into omap-for-v4.17/timer (2018-02-22 10:46:47 -0800)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.17/timer-signed
> >
> > for you to fetch changes up to 58a54f03e73d67432216931854363e4ba15839b9:
> >
> > clocksource: timer-ti-dm: Check prescaler value (2018-02-28 13:41:30 -0800)
> >
> > ----------------------------------------------------------------
> > Move omap timer to drivers for 4.17
> >
> > This series from Keerthy and Ladislav Michl move omap dmtimer code
> > to drivers. As we don't want to export custom timer functions to
> > random drivers, we also need to update the related PWM driver to
> > pass the timer specific functions in platform data.
> >
> > Note that this series is based on a merge of omap1 specific timer
> > fix and omap2+ platform data clean-up to keep things working and
> > make the move a bit simpler.
>
> I was undecided whether this should be in next/drivers or next/soc,
> ended up putting it into the latter.
>
> I don't see the clocksource maintainers involved in the patch series,
> so I added them to Cc now to make sure they are aware of the move
> of the driver.
OK thanks. We got some comments from Daniel for an earlier set of
patches in December. No acks though, but hopefully it's good enough
for further work to happen under drivers/clocksource :)
Regards,
Tony
next prev parent reply other threads:[~2018-03-07 15:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 18:11 [GIT PULL 1/6] omap soc changes for v4.17 Tony Lindgren
2018-03-05 18:11 ` [GIT PULL 2/6] omap timer " Tony Lindgren
2018-03-07 15:21 ` Arnd Bergmann
2018-03-07 15:28 ` Tony Lindgren [this message]
2018-03-07 16:21 ` Daniel Lezcano
2018-03-05 18:11 ` [GIT PULL 3/6] am335x and am437x pm " Tony Lindgren
2018-03-07 15:26 ` Arnd Bergmann
2018-03-05 18:11 ` [GIT PULL 4/6] ti-sysc changes " Tony Lindgren
2018-03-07 15:27 ` Arnd Bergmann
2018-03-05 18:11 ` [GIT PULL 5/6] omap dts " Tony Lindgren
2018-03-07 14:39 ` Arnd Bergmann
2018-03-05 18:11 ` [GIT PULL 6/6] dra7 sdhci " Tony Lindgren
2018-03-07 14:40 ` Arnd Bergmann
2018-03-07 15:04 ` Tony Lindgren
2018-03-07 15:07 ` Arnd Bergmann
2018-03-07 15:15 ` [GIT PULL 1/6] omap soc " Arnd Bergmann
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=20180307152842.GH5799@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@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