From: Shuah Khan <shuahkh@osg.samsung.com>
To: John Stultz <john.stultz@linaro.org>,
lkml <linux-kernel@vger.kernel.org>
Cc: Sasha Levin <sasha.levin@oracle.com>,
Richard Cochran <richardcochran@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Prarit Bhargava <prarit@redhat.com>,
Harald Hoyer <harald@redhat.com>, Kay Sievers <kay@vrfy.org>,
David Herrmann <dh.herrmann@gmail.com>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 0/2] Fix for ADJ_SETOFFSET w/ ADJ_NANO
Date: Thu, 21 Jan 2016 16:16:55 -0700 [thread overview]
Message-ID: <56A166E7.3070601@osg.samsung.com> (raw)
In-Reply-To: <1453417415-19110-1-git-send-email-john.stultz@linaro.org>
On 01/21/2016 04:03 PM, John Stultz wrote:
> David Herrmann mailed me pointing out that one of the
> changes that landed in 4.5-rc broke users of ADJ_SETOFFSET
> when used with ADJ_NANO.
>
> I've implemented a fix to this issue and also introduced
> more unit tests to validate these going forward.
>
> Thomas: Can you queue the first patch for tip/timers/urgent?
>
> Shuah: The kselftests patch can wait to the next merge window
> if you'd prefer.
Yeah. Probably it has to wait until the next merge window as
this is a new test. I can pull this into linux-kselftest next
after merge window closes.
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
next prev parent reply other threads:[~2016-01-21 23:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 23:03 John Stultz
2016-01-21 23:03 ` [PATCH 1/2] ntp: Fix ADJ_SETOFFSET being used " John Stultz
2016-01-22 11:06 ` David Herrmann
2016-01-22 11:06 ` [tip:timers/urgent] " tip-bot for John Stultz
2016-01-21 23:03 ` [PATCH 2/2] kselftests: timers: Add adjtimex SETOFFSET validity tests John Stultz
2016-01-26 15:39 ` [tip:timers/urgent] " tip-bot for John Stultz
2016-01-21 23:16 ` Shuah Khan [this message]
2016-01-22 7:54 ` [PATCH 0/2] Fix for ADJ_SETOFFSET w/ ADJ_NANO Thomas Gleixner
2016-01-22 14:56 ` Shuah Khan
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=56A166E7.3070601@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=dh.herrmann@gmail.com \
--cc=harald@redhat.com \
--cc=john.stultz@linaro.org \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=richardcochran@gmail.com \
--cc=sasha.levin@oracle.com \
--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
Powered by JetHome