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,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] iopoll: fix function parameter names in read_poll_timeout_atomic()
Date: Mon, 09 Mar 2026 12:35:11 +0200 [thread overview]
Message-ID: <d1ea41327832c2e4447429d6fc0030b71491ca44@intel.com> (raw)
In-Reply-To: <20260306221033.2357305-1-rdunlap@infradead.org>
On Fri, 06 Mar 2026, Randy Dunlap <rdunlap@infradead.org> wrote:
> Correct the function parameter names to avoid kernel-doc warnings
> and to emphasize this function is atomic (non-sleeping).
>
> 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'
>
> Fixes: 9df8043a546d ("iopoll: Generalize read_poll_timeout() into poll_timeout_us()")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Please let me know how you want this merged. I don't think iopoll.h has
an active maintainer.
> ---
> v2: change the function parameter names, not the kernel-doc comments (Jani)
>
> include/linux/iopoll.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> --- linux-next-20260304.orig/include/linux/iopoll.h
> +++ linux-next-20260304/include/linux/iopoll.h
> @@ -159,7 +159,7 @@
> *
> * 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 @delay_us.
> *
> * When available, you'll probably want to use one of the specialized
> * macros defined below rather than this macro directly.
> @@ -167,9 +167,9 @@
> * Returns: 0 on success and -ETIMEDOUT upon a timeout. In either
> * case, the last read value at @args is stored in @val.
> */
> -#define read_poll_timeout_atomic(op, val, cond, sleep_us, timeout_us, \
> - sleep_before_read, args...) \
> - poll_timeout_us_atomic((val) = op(args), cond, sleep_us, timeout_us, sleep_before_read)
> +#define read_poll_timeout_atomic(op, val, cond, delay_us, timeout_us, \
> + delay_before_read, args...) \
> + poll_timeout_us_atomic((val) = op(args), cond, delay_us, timeout_us, delay_before_read)
>
> /**
> * readx_poll_timeout - Periodically poll an address until a condition is met or a timeout occurs
>
>
> ---
> 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
> Cc: dri-devel@lists.freedesktop.org
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-03-09 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 22:10 [PATCH v2] iopoll: fix function parameter names in read_poll_timeout_atomic() Randy Dunlap
2026-03-07 5:13 ` ✓ CI.KUnit: success for " Patchwork
2026-03-07 6:16 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-08 10:18 ` ✓ Xe.CI.FULL: success " Patchwork
2026-03-09 10:35 ` Jani Nikula [this message]
2026-03-09 16:56 ` [PATCH v2] " Randy Dunlap
2026-03-10 8:50 ` Jani Nikula
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=d1ea41327832c2e4447429d6fc0030b71491ca44@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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