From: Waiman Long <longman@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Davidlohr Bueso <dave@stgolabs.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Tim Chen <tim.c.chen@linux.intel.com>,
huang ying <huang.ying.caritas@gmail.com>
Subject: Re: [PATCH-tip 0/2] locking/rwsem: Rwsem rearchitecture part 2 follow-up patches
Date: Thu, 18 Apr 2019 08:42:42 -0400 [thread overview]
Message-ID: <a5d28322-fe37-fc88-6127-2f8abba81afe@redhat.com> (raw)
In-Reply-To: <20190418080202.GA13653@gmail.com>
On 04/18/2019 04:02 AM, Ingo Molnar wrote:
> * Waiman Long <longman@redhat.com> 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.
Cheers,
Longman
prev parent reply other threads:[~2019-04-18 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 20:58 [PATCH-tip 0/2] locking/rwsem: Rwsem rearchitecture part 2 follow-up patches Waiman Long
2019-04-15 20:58 ` [PATCH-tip 1/2] locking/rwsem: Clarify usage of owner's nonspinaable bit Waiman Long
2019-04-15 20:58 ` [PATCH-tip 2/2] locking/rwsem: Adaptive disabling of reader optimistic spinning Waiman Long
2019-04-16 13:10 ` [PATCH-tip 0/2] locking/rwsem: Rwsem rearchitecture part 2 follow-up patches Peter Zijlstra
2019-04-16 13:18 ` Waiman Long
2019-04-16 14:17 ` Peter Zijlstra
2019-04-16 17:03 ` Waiman Long
2019-04-16 17:37 ` Peter Zijlstra
2019-04-16 19:49 ` Waiman Long
2019-04-17 5:57 ` Ingo Molnar
2019-04-17 20:30 ` Waiman Long
2019-04-18 8:02 ` Ingo Molnar
2019-04-18 12:42 ` Waiman Long [this message]
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=a5d28322-fe37-fc88-6127-2f8abba81afe@redhat.com \
--to=longman@redhat.com \
--cc=dave@stgolabs.net \
--cc=huang.ying.caritas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).