public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
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: Tue, 18 Sep 2012 07:39:55 +0200	[thread overview]
Message-ID: <20120918053955.GA24058@1wt.eu> (raw)
In-Reply-To: <1347935530-33767-1-git-send-email-john.stultz@linaro.org>

Hi John,

On Mon, Sep 17, 2012 at 10:32:07PM -0400, John Stultz wrote:
> Just wanted to send out a few timekeeping fixes that were merged
> in 3.6 which are appropriate for -stable.

Thank you very much, I'm adding them to your last ones. I have not released
the version yet but they're not lost. I will then release all of them at once.

Best regards,
Willy


  parent reply	other threads:[~2012-09-18  5:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18  2:32 [PATCH 0/3] 3.2-stable timekeeping fixes merged in 3.6 John Stultz
2012-09-18  2:32 ` [PATCH 1/3] 2.6.32.y: time: Improve sanity checking of timekeeping inputs John Stultz
2012-09-18  2:32 ` [PATCH 2/3] 2.6.32.y: time: Avoid making adjustments if we haven't accumulated anything John Stultz
2012-09-18  2:32 ` [PATCH 3/3] 2.6.32.y: time: Move ktime_t overflow checking into timespec_valid_strict John Stultz
2012-09-18  2:49 ` [PATCH 0/3] 3.2-stable timekeeping fixes merged in 3.6 John Stultz
2012-09-18  5:39 ` Willy Tarreau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-09-11 22:35 John Stultz
2012-09-16 15:59 ` Ben Hutchings
2012-09-27 20:39 ` Greg KH
2012-09-27 20:39   ` Greg KH
2012-09-27 21:48   ` 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=20120918053955.GA24058@1wt.eu \
    --to=w@1wt.eu \
    --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