From: Peter Zijlstra <peterz@infradead.org>
To: John Stultz <jstultz@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Juri Lelli <juri.lelli@redhat.com>,
Metin Kaya <metin.kaya@arm.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] locking: Fix warning from missing argument documentation
Date: Mon, 14 Oct 2024 12:53:23 +0200 [thread overview]
Message-ID: <20241014105323.GA16066@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20241012165523.2856425-1-jstultz@google.com>
On Sat, Oct 12, 2024 at 09:54:37AM -0700, John Stultz wrote:
> The kernel test robot complained the commit 8d8fcb8c6a67
> ("locking/mutex: Remove wakeups from under mutex::wait_lock"),
> currently only in Peter's git tree, didn't update the kernel doc
> for the new wake_q argument added.
I have folded this and a fix for the i386-randconfig build problem, and
pushed out again.
next prev parent reply other threads:[~2024-10-14 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202410121433.jYN4ypTb-lkp@intel.com>
2024-10-12 16:54 ` [PATCH] locking: Fix warning from missing argument documentation John Stultz
2024-10-14 10:53 ` Peter Zijlstra [this message]
2024-10-14 17:08 ` 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=20241014105323.GA16066@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=metin.kaya@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