From: Greg KH <greg@kroah.com>
To: John Stultz <john.stultz@linaro.org>
Cc: stable@vger.kernel.org, Prarit Bhargava <prarit@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] 3.5-stable timekeeping fixes merged in 3.6
Date: Thu, 27 Sep 2012 13:30:46 -0700 [thread overview]
Message-ID: <20120927203046.GA19489@kroah.com> (raw)
In-Reply-To: <1347389781-54602-1-git-send-email-john.stultz@linaro.org>
On Tue, Sep 11, 2012 at 02:56:18PM -0400, John Stultz wrote:
> Just wanted to send out a few timekeeping fixes that were merged
> in 3.6 which are appropriate for -stable.
>
> This queue backports the following fixes:
> -----------------------------------------
> cee58483cf56e0ba355fdd97ff5e8925329aa936 time: Move ktime_t overflow checking into timespec_valid_strict
> bf2ac312195155511a0f79325515cbb61929898a time: Avoid making adjustments if we haven't accumulated anything
> 4e8b14526ca7fb046a81c94002c1c43b6fdf0e9b time: Improve sanity checking of timekeeping inputs
>
> I've run these through my timetest suite w/ kvm on both i386
> & x86_64. But more testing would be of course appreciated.
> https://github.com/johnstultz-work/timetests
>
> I also have patch queues for all the -stable trees that I'll be
> sending out as my testing completes for those trees.
Applied, thanks.
greg k-h
prev parent reply other threads:[~2012-09-27 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 18:56 [PATCH 0/3] 3.5-stable timekeeping fixes merged in 3.6 John Stultz
2012-09-11 18:56 ` [PATCH 1/3] 3.5.y: time: Improve sanity checking of timekeeping inputs John Stultz
2012-09-27 20:49 ` Patch "time: Improve sanity checking of timekeeping inputs" has been added to the 3.5-stable tree gregkh
2012-09-11 18:56 ` [PATCH 2/3] 3.5.y: time: Avoid making adjustments if we haven't accumulated anything John Stultz
2012-09-11 18:56 ` [PATCH 3/3] 3.5.y: time: Move ktime_t overflow checking into timespec_valid_strict John Stultz
2012-09-27 20:30 ` Greg KH [this message]
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=20120927203046.GA19489@kroah.com \
--to=greg@kroah.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.