[lkml]   [2019]   [Apr]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH-tip 0/2] locking/rwsem: Rwsem rearchitecture part 2 follow-up patches
On 04/18/2019 04:02 AM, Ingo Molnar wrote:
> * Waiman Long <> wrote:
>> As the part2 patches are still being actively modified, it doesn't look
>> like it will make the next merge window. I am fine with postponing it
>> to 5.3. However, I would like to request the merging of just patch 1 of
>> the part 2 patchset. It fixes a locking selftest problem that was
>> introduced in the part 1 patches.
> Sure, I've promoted this commit:
> 26536e7c242e: locking/rwsem: Prevent unneeded warning during locking selftest
> from tip:WIP.locking/core into tip:locking/core, for a v5.2 merge.
> Thanks,
> Ingo

Thanks for the help. I just don't want to get report of known problem
during the next merge window.


 \ /
  Last update: 2019-04-18 14:43    [W:0.048 / U:1.256 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site