mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org
Cc: "Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Marco Elver <elver@google.com>,
	x86@kernel.org
Subject: Re: [tip: locking/core] locking: Fix rwlock and spinlock lock context annotations
Date: Thu, 12 Mar 2026 09:36:09 -0700	[thread overview]
Message-ID: <66c850f8-c4bd-4387-881e-01d3e1f402c4@acm.org> (raw)
In-Reply-To: <177227618921.1647592.10577654819420686202.tip-bot2@tip-bot2>

On 2/28/26 2:56 AM, tip-bot2 for Bart Van Assche wrote:
> The following commit has been merged into the locking/core branch of tip:
> 
> Commit-ID:     38e18d825f7281fdc16d3241df5115ce6eaeaf79
> Gitweb:        https://git.kernel.org/tip/38e18d825f7281fdc16d3241df5115ce6eaeaf79
> Author:        Bart Van Assche <bvanassche@acm.org>
> AuthorDate:    Wed, 25 Feb 2026 10:32:41 -08:00
> Committer:     Peter Zijlstra <peterz@infradead.org>
> CommitterDate: Fri, 27 Feb 2026 16:40:19 +01:00
> 
> locking: Fix rwlock and spinlock lock context annotations

Hi Peter,

Thank you for having queued this patch.

Since some of my other patches depend on this patch, will this patch be
sent to Linus during the current rc cycle? I'm asking this because I
can't find this patch in Linus' master branch:

$ git fetch origin
$ git log --reverse --format=oneline v6.19..origin/master 
include/linux/rwlock_api_smp.h
f16a802d402d735a55731f8c94952b3bbb5ddfe8 locking/rwlock, spinlock: 
Support Clang's context analysis
e4588c25c9d122b5847b88e18b184404b6959160 compiler-context-analysis: 
Remove __cond_lock() function-like helper
7a562d5d2396c9c78fbbced7ae81bcfcfa0fde3f (tag: locking-core-2026-02-08) 
locking/rwlock: Fix write_trylock_irqsave() with CONFIG_INLINE_WRITE_TRYLOCK

Thanks,

Bart.

  reply	other threads:[~2026-03-12 16:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 18:32 [PATCH v2 0/4] Lock context annotation fixes Bart Van Assche
2026-02-25 18:32 ` [PATCH v2 1/4] locking: Fix rwlock and spinlock lock context annotations Bart Van Assche
2026-02-28 10:56   ` [tip: locking/core] " tip-bot2 for Bart Van Assche
2026-03-12 16:36     ` Bart Van Assche [this message]
2026-02-25 18:32 ` [PATCH v2 2/4] signal: Fix the lock_task_sighand() annotation Bart Van Assche
2026-02-28 10:56   ` [tip: locking/core] " tip-bot2 for Bart Van Assche
2026-02-25 18:32 ` [PATCH v2 3/4] ww-mutex: Fix the ww_acquire_ctx function annotations Bart Van Assche
2026-02-28 10:56   ` [tip: locking/core] " tip-bot2 for Bart Van Assche
2026-02-25 18:32 ` [PATCH v2 4/4] Revert "lockdep: Annotate lockdep assertions for context analysis" Bart Van Assche
2026-02-25 18:40   ` Marco Elver
2026-02-25 19:22     ` Marco Elver
2026-02-25 19:27     ` Bart Van Assche
2026-02-25 18:44 ` [PATCH v2 0/4] Lock context annotation fixes Marco Elver

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=66c850f8-c4bd-4387-881e-01d3e1f402c4@acm.org \
    --to=bvanassche@acm.org \
    --cc=elver@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=peterz@infradead.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®