From: Jani Nikula <jani.nikula@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: "Randy Dunlap" <rdunlap@infradead.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH RESEND] iopoll: fix parameter names in kernel-doc
Date: Fri, 06 Mar 2026 12:31:54 +0200 [thread overview]
Message-ID: <7b4ab61091b0bd032e129e46237f707d2448ca08@intel.com> (raw)
In-Reply-To: <20260306063829.2059375-1-rdunlap@infradead.org>
On Thu, 05 Mar 2026, Randy Dunlap <rdunlap@infradead.org> wrote:
> Correct the parameter names to avoid kernel-doc warnings:
>
> Warning: include/linux/iopoll.h:169 function parameter 'sleep_us' not
> described in 'read_poll_timeout_atomic'
> Warning: ../include/linux/iopoll.h:169 function parameter
> 'sleep_before_read' not described in 'read_poll_timeout_atomic'
I think the right fix is to rename the parameters instead. They're
passed on to poll_timeout_us_atomic() where the parameters are called
delay_us and delay_before_op, emphasizing that this is atomic i.e. no
sleep.
BR,
Jani.
>
> Fixes: 9df8043a546d ("iopoll: Generalize read_poll_timeout() into poll_timeout_us()")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: intel-gfx@lists.freedesktop.org
> Cc: intel-xe@lists.freedesktop.org
> ---
> include/linux/iopoll.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> --- linux-next-20260304.orig/include/linux/iopoll.h
> +++ linux-next-20260304/include/linux/iopoll.h
> @@ -150,16 +150,16 @@
> * @op: accessor function (takes @args as its arguments)
> * @val: Variable to read the value into
> * @cond: Break condition (usually involving @val)
> - * @delay_us: Time to udelay between reads in us (0 tight-loops). Please
> + * @sleep_us: Time to udelay between reads in us (0 tight-loops). Please
> * read udelay() function description for details and
> * limitations.
> * @timeout_us: Timeout in us, 0 means never timeout
> - * @delay_before_read: if it is true, delay @delay_us before read.
> + * @sleep_before_read: if it is true, delay @sleep_us before read.
> * @args: arguments for @op poll
> *
> * This macro does not rely on timekeeping. Hence it is safe to call even when
> * timekeeping is suspended, at the expense of an underestimation of wall clock
> - * time, which is rather minimal with a non-zero delay_us.
> + * time, which is rather minimal with a non-zero @sleep_us.
> *
> * When available, you'll probably want to use one of the specialized
> * macros defined below rather than this macro directly.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-03-06 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 6:38 [PATCH RESEND] iopoll: fix parameter names in kernel-doc Randy Dunlap
2026-03-06 10:31 ` Jani Nikula [this message]
2026-03-06 19:39 ` Randy Dunlap
2026-03-06 18:41 ` ✓ CI.KUnit: success for iopoll: fix parameter names in kernel-doc (rev2) Patchwork
2026-03-06 19:26 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-07 21:17 ` ✗ Xe.CI.FULL: failure " Patchwork
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=7b4ab61091b0bd032e129e46237f707d2448ca08@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=ville.syrjala@linux.intel.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