From: Jani Nikula <jani.nikula@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: "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: Tue, 10 Mar 2026 10:50:01 +0200 [thread overview]
Message-ID: <8b4fb7cdc116b3d4ed78295f70e263daaf86b7e6@intel.com> (raw)
In-Reply-To: <f57f964c-d4c2-41d7-86ce-6db11b0601e4@infradead.org>
On Mon, 09 Mar 2026, Randy Dunlap <rdunlap@infradead.org> wrote:
> On 3/9/26 3:35 AM, Jani Nikula wrote:
>> 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.
>
> Right, that's why I Cc-ed you :)
> And since Fixes: points to you and others.
> Please take it, Jani.
Thanks for the fix, pushed to drm-intel-next.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2026-03-10 8:50 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 ` [PATCH v2] " Jani Nikula
2026-03-09 16:56 ` Randy Dunlap
2026-03-10 8:50 ` Jani Nikula [this message]
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=8b4fb7cdc116b3d4ed78295f70e263daaf86b7e6@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