From: Nathan Lynch <nathan_lynch@mentor.com>
To: <linux-arm-kernel@lists.infradead.org>
Cc: Russell King <linux@arm.linux.org.uk>,
John Stultz <john.stultz@linaro.org>,
Will Deacon <will.deacon@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] fix vdso coarse clock monotonicity regressions
Date: Fri, 7 Aug 2015 21:03:21 -0500 [thread overview]
Message-ID: <1438999403-5770-1-git-send-email-nathan_lynch@mentor.com> (raw)
Commit 906c55579a63 ("timekeeping: Copy the shadow-timekeeper over the
real timekeeper last") made it so the user can observe the coarse
clocks going backwards on arm and arm64, if they're really looking for
it.
Technically these are fixing regressions versus 4.1, but I won't be
bothered if they don't make 4.2 final at this late stage, since only
the (seldom-used?) coarse clocks are affected.
I'd like to collect review/acks for these now and make sure they at
least make it into 4.3-rc1 (and -stable after that).
Nathan Lynch (2):
ARM: VDSO: fix coarse clock monotonicity regression
arm64: VDSO: fix coarse clock monotonicity regression
arch/arm/kernel/vdso.c | 7 +++----
arch/arm64/kernel/vdso.c | 7 +++----
2 files changed, 6 insertions(+), 8 deletions(-)
--
2.1.0
next reply other threads:[~2015-08-08 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 2:03 Nathan Lynch [this message]
2015-08-08 2:03 ` [PATCH 1/2] ARM: VDSO: fix coarse clock monotonicity regression Nathan Lynch
2015-08-10 9:08 ` Will Deacon
2015-08-08 2:03 ` [PATCH 2/2] arm64: " Nathan Lynch
2015-08-10 9:22 ` Will Deacon
2015-08-10 14:58 ` Catalin Marinas
2015-08-12 20:00 ` John Stultz
2015-08-10 15:46 ` [PATCH v2] ARM: " Nathan Lynch
2015-08-10 15:48 ` Will Deacon
2015-08-12 20:00 ` John Stultz
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=1438999403-5770-1-git-send-email-nathan_lynch@mentor.com \
--to=nathan_lynch@mentor.com \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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
all inboxes | Powered by JetHome®