From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Bartosz Golaszewski" <bgolaszewski@baylibre.com>,
"Arnd Bergmann" <arnd@kernel.org>,
"Claudiu Beznea" <Claudiu.Beznea@microchip.com>,
j.neuschaefer@gmx.net
Subject: [GIT PULL] timer drivers for v5.12
Date: Tue, 9 Feb 2021 22:51:54 +0100 [thread overview]
Message-ID: <3747fbde-134f-5e1d-47d5-8776c1a52aa1@linaro.org> (raw)
Hi Thomas,
please consider pulling the following changes for v5.12.
Thanks
-- Daniel
The following changes since commit e85c1d21b16b278f50d191155bc674633270e9c6:
clocksource/drivers/timer-microchip-pit64b: Add clocksource
suspend/resume (2021-02-03 09:36:50 +0100)
are available in the Git repository at:
https://git.linaro.org/people/daniel.lezcano/linux.git
tags/timers-v5.12-rc1
for you to fetch changes up to e85c1d21b16b278f50d191155bc674633270e9c6:
clocksource/drivers/timer-microchip-pit64b: Add clocksource
suspend/resume (2021-02-03 09:36:50 +0100)
----------------------------------------------------------------
- Drop dead code on efm32 (Uwe Kleine-König)
- Move pr_fmt() before the includes on davinci driver (Bartosz
Golaszewski)
- Clarified timer interrupt must be specified on nuvoton DT bindings
(Jonathan Neuschäfer)
- Remove tango, sirf, u300 and atlas timer drivers (Arnd Bergman)
- Add suspend/resume on pit64b (Claudiu Beznea)
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next reply other threads:[~2021-02-10 1:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 21:51 Daniel Lezcano [this message]
2021-02-10 10:06 ` [tip: timers/core] Merge tag 'timers-v5.12-rc1' of https://git.linaro.org/people/daniel.lezcano/linux into timers/core tip-bot2 for Thomas Gleixner
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=3747fbde-134f-5e1d-47d5-8776c1a52aa1@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=Claudiu.Beznea@microchip.com \
--cc=arnd@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=j.neuschaefer@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.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).