From: Greg KH <gregkh@linuxfoundation.org>
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.2-stable timekeeping fixes merged in 3.6
Date: Thu, 27 Sep 2012 13:39:11 -0700 [thread overview]
Message-ID: <20120927203911.GC19489@kroah.com> (raw)
In-Reply-To: <1347402926-34813-1-git-send-email-john.stultz@linaro.org>
On Tue, Sep 11, 2012 at 06:35:23PM -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.
Did you also send these out for the 3.0.y tree and I just missed them?
Should I just take this 3.2.y series and see how they well apply?
thanks,
greg k-h
next prev parent reply other threads:[~2012-09-27 20:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 22:35 [PATCH 0/3] 3.2-stable timekeeping fixes merged in 3.6 John Stultz
2012-09-11 22:35 ` [PATCH 1/3] 3.2.y: time: Improve sanity checking of timekeeping inputs John Stultz
2012-09-11 22:35 ` [PATCH 2/3] 3.2.y: time: Avoid making adjustments if we haven't accumulated anything John Stultz
2012-09-11 22:35 ` [PATCH 3/3] 3.2.y: time: Move ktime_t overflow checking into timespec_valid_strict John Stultz
2012-09-16 15:59 ` [PATCH 0/3] 3.2-stable timekeeping fixes merged in 3.6 Ben Hutchings
2012-09-27 20:39 ` Greg KH [this message]
2012-09-27 20:39 ` Greg KH
2012-09-27 21:48 ` John Stultz
-- strict thread matches above, loose matches on Subject: below --
2012-09-18 2:32 John Stultz
2012-09-18 2:49 ` John Stultz
2012-09-18 5:39 ` Willy Tarreau
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=20120927203911.GC19489@kroah.com \
--to=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox