mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: John Stultz <jstultz@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	syzbot+602c4720aed62576cd79@syzkaller.appspotmail.com,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	Ingo Molnar <mingo@redhat.com>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Valentin Schneider <valentin.schneider@arm.com>,
	Suleiman Souhlal <suleiman@google.com>,
	airlied@gmail.com, mripard@kernel.org, simona@ffwll.ch,
	tzimmermann@suse.de, dri-devel@lists.freedesktop.org,
	kernel-team@android.com
Subject: Re: [PATCH v3] locking: Fix __clear_task_blocked_on() warning from __ww_mutex_wound() path
Date: Mon, 11 Aug 2025 18:21:37 +0200	[thread overview]
Message-ID: <20250811162137.GB4067720@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <d737c0f0-c0e0-4df5-8246-b484db8d061b@linux.intel.com>

On Tue, Aug 05, 2025 at 11:27:47AM +0200, Maarten Lankhorst wrote:
> Acked-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>

Thanks both!

  reply	other threads:[~2025-08-11 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01 19:21 [PATCH v2] " John Stultz
2025-08-04  4:42 ` K Prateek Nayak
2025-08-05  0:10 ` [PATCH v3] " John Stultz
2025-08-05  9:27   ` Maarten Lankhorst
2025-08-11 16:21     ` Peter Zijlstra [this message]
2025-08-13 13:18   ` [tip: locking/urgent] " tip-bot2 for John Stultz

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=20250811162137.GB4067720@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=airlied@gmail.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jstultz@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=kernel-team@android.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mingo@redhat.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=suleiman@google.com \
    --cc=syzbot+602c4720aed62576cd79@syzkaller.appspotmail.com \
    --cc=tzimmermann@suse.de \
    --cc=valentin.schneider@arm.com \
    --cc=vincent.guittot@linaro.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®