All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] locking changes for v6.2
Date: Mon, 12 Dec 2022 21:16:13 +0100	[thread overview]
Message-ID: <Y5eMDYABnSszN9/s@gmail.com> (raw)

Linus,

Please pull the latest locking tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-core-2022-12-12

   # HEAD: 90d758896787048fa3d4209309d4800f3920e66f futex: Resend potentially swallowed owner death notification

Two changes in this cycle:

 - a micro-optimization in static_key_slow_inc_cpuslocked()
 - fix futex death-notification wakeup bug

 Thanks,

	Ingo

------------------>
Alexey Izbyshev (1):
      futex: Resend potentially swallowed owner death notification

Uros Bizjak (1):
      jump_label: Use atomic_try_cmpxchg() in static_key_slow_inc_cpuslocked()


 kernel/futex/core.c | 26 +++++++++++++++++---------
 kernel/jump_label.c |  8 ++------
 2 files changed, 19 insertions(+), 15 deletions(-)

             reply	other threads:[~2022-12-12 20:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 20:16 Ingo Molnar [this message]
2022-12-12 23:45 ` [GIT PULL] locking changes for v6.2 pr-tracker-bot
2023-02-20 12:25 ` [GIT PULL] locking changes for v6.3 Ingo Molnar
2023-02-21  1:52   ` pr-tracker-bot
2023-04-27 19:58   ` [GIT PULL] locking changes for v6.4 Ingo Molnar
2023-04-28 21:40     ` Linus Torvalds
2023-04-29  6:47       ` Ingo Molnar
2023-05-04 17:28         ` Andrzej Hajda
2023-05-04 18:23           ` Linus Torvalds

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=Y5eMDYABnSszN9/s@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=boqun.feng@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.