From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] locking/urgent for v6.13-rc3
Date: Mon, 9 Dec 2024 11:17:47 +0100 [thread overview]
Message-ID: <20241209101747.GAZ1bDy7XMTKoRqs1g@fat_crate.local> (raw)
Hi Linus,
please pull the locking/urgent lineup for v6.13-rc3.
Thx.
---
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip tags/locking_urgent_for_v6.13_rc3
for you to fetch changes up to b4d83c8323b0c4a899a996fed919cfe10720d289:
headers/cleanup.h: Remove the if_not_guard() facility (2024-12-07 11:15:14 +0100)
----------------------------------------------------------------
- Remove if_not_guard() as it is generating incorrect code
- Fix the initialization of the fake lockdep_map for the first locked
ww_mutex
----------------------------------------------------------------
Ingo Molnar (1):
headers/cleanup.h: Remove the if_not_guard() facility
Thomas Hellström (1):
locking/ww_mutex: Fix ww_mutex dummy lockdep map selftest warnings
include/linux/cleanup.h | 14 --------------
include/linux/ww_mutex.h | 4 ++--
lib/locking-selftest.c | 4 ++--
3 files changed, 4 insertions(+), 18 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2024-12-09 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 10:17 Borislav Petkov [this message]
2024-12-09 18:38 ` 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=20241209101747.GAZ1bDy7XMTKoRqs1g@fat_crate.local \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®