[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56A24306.7070807@osg.samsung.com>
Date: Fri, 22 Jan 2016 07:56:06 -0700
From: Shuah Khan <shuahkh@....samsung.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: John Stultz <john.stultz@...aro.org>,
lkml <linux-kernel@...r.kernel.org>,
Sasha Levin <sasha.levin@...cle.com>,
Richard Cochran <richardcochran@...il.com>,
Prarit Bhargava <prarit@...hat.com>,
Harald Hoyer <harald@...hat.com>, Kay Sievers <kay@...y.org>,
David Herrmann <dh.herrmann@...il.com>
Subject: Re: [PATCH 0/2] Fix for ADJ_SETOFFSET w/ ADJ_NANO
On 01/22/2016 12:54 AM, Thomas Gleixner wrote:
> On Thu, 21 Jan 2016, Shuah Khan wrote:
>> 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.
>
> We really should not delay selftests, especially if they have been written
> along with a fix for a recently detected problem.
>
Thomas,
Yes. That is why I have "probably" in my response.
Could you please fold this test in with your urgent
fix, so they can go in together.
Acked-by: Shuah Khan <shuahkh@....samsung.com>
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@....samsung.com | (970) 217-8978
Powered by blists - more mailing lists