From: Waiman Long <longman9394@gmail.com>
To: Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Will Deacon <will.deacon@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] locking changes for v5.2
Date: Mon, 6 May 2019 12:11:41 -0400 [thread overview]
Message-ID: <a5ee37fe-bdcf-2da7-4f02-6d64b4dcd2d3@gmail.com> (raw)
In-Reply-To: <20190506085014.GA130963@gmail.com>
On 5/6/19 4:50 AM, Ingo Molnar wrote:
> Linus,
>
> Please pull the latest locking-core-for-linus git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-core-for-linus
>
> # HEAD: d671002be6bdd7f77a771e23bf3e95d1f16775e6 locking/lockdep: Remove unnecessary unlikely()
>
> [ Dependency note: this tree depends on commits also in the RCU tree,
> please disregard this pull request if you weren't able to pull the RCU
> tree for some reason. ]
>
> Here are the locking changes in this cycle:
>
> - rwsem unification and simpler micro-optimizations to prepare for more
> intrusive (and more lucrative) scalability improvements in v5.3
> (Waiman Long)
Is it possible to pull in also my "locking/rwsem: Prevent decrement of
reader count before increment" patch for 5.2? The rests can wait until 5.3.
Thanks,
Longman
next prev parent reply other threads:[~2019-05-06 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 8:50 [GIT PULL] locking changes for v5.2 Ingo Molnar
2019-05-06 16:11 ` Waiman Long [this message]
2019-05-06 19:43 ` Ingo Molnar
2019-05-06 20:55 ` Linus Torvalds
2019-05-06 22:39 ` Ingo Molnar
2019-05-07 8:24 ` Ingo Molnar
2019-05-07 14:39 ` Waiman Long
2019-05-06 23:40 ` pr-tracker-bot
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=a5ee37fe-bdcf-2da7-4f02-6d64b4dcd2d3@gmail.com \
--to=longman9394@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
/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).