From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arch_timer updates for v4.15
Date: Mon, 16 Oct 2017 16:28:37 +0100 [thread overview]
Message-ID: <20171016152839.14964-1-mark.rutland@arm.com> (raw)
Hi Daniel,
Please could you pull these arch timer updates for v4.15?
The first patch is a fix from Ard that fixes probling the MMIO timers on some
platforms. The other patch is a minor cleanup that prevents a warning when
building tags.
Thanks,
Mark.
The following changes since commit 9e66317d3c92ddaab330c125dfe9d06eee268aff:
Linux 4.14-rc3 (2017-10-01 14:54:54 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git tags/arch-timer-4.15
for you to fetch changes up to cb3a23a029f6af0c73498b6a9773d6ec19541bf1:
clocksource: arm_arch_timer: fix DEFINE_PER_CPU expansion (2017-10-16 15:37:16 +0100)
----------------------------------------------------------------
arch_timer updates for v4.15
- enable the MMIO CNTFRQ before reading it
- avoid a warning when building tags
----------------------------------------------------------------
Ard Biesheuvel (1):
clocksource: arm_arch_timer: validate CNTFRQ after enabling frame
Mark Rutland (1):
clocksource: arm_arch_timer: fix DEFINE_PER_CPU expansion
drivers/clocksource/arm_arch_timer.c | 41 +++++++++++++++++++-----------------
1 file changed, 22 insertions(+), 19 deletions(-)
next reply other threads:[~2017-10-16 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 15:28 Mark Rutland [this message]
2017-10-16 15:28 ` [PATCH 1/2] clocksource: arm_arch_timer: validate CNTFRQ after enabling frame Mark Rutland
2017-10-16 15:28 ` [PATCH 2/2] clocksource: arm_arch_timer: fix DEFINE_PER_CPU expansion Mark Rutland
2017-10-16 16:12 ` [PATCH] checkpatch: Allow DEFINE_PER_CPU definitions to exceed line length Joe Perches
2017-10-16 16:32 ` Mark Rutland
2017-10-17 18:16 ` [GIT PULL] arch_timer updates for v4.15 Daniel Lezcano
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=20171016152839.14964-1-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).