From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Kriish Sharma <kriish.sharma2006@gmail.com>
Cc: <lucas.demarchi@intel.com>, <thomas.hellstrom@linux.intel.com>,
<airlied@gmail.com>, <simona@ffwll.ch>,
<intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH] drm/xe: fix kernel-doc function name mismatch in xe_pm.c
Date: Mon, 10 Nov 2025 14:02:30 -0500 [thread overview]
Message-ID: <aRI2xnMDl2h4icmr@intel.com> (raw)
In-Reply-To: <20251110184206.2113830-1-kriish.sharma2006@gmail.com>
On Mon, Nov 10, 2025 at 06:42:06PM +0000, Kriish Sharma wrote:
> Documentation build reported:
>
> WARNING: ./drivers/gpu/drm/xe/xe_pm.c:131 expecting prototype for xe_pm_might_block_on_suspend(). Prototype was for xe_pm_block_on_suspend() instead
>
> The kernel-doc comment for xe_pm_block_on_suspend() incorrectly used
> the function name xe_pm_might_block_on_suspend(). Fix the header to
> match the actual function prototype.
>
> No functional changes.
>
> Fixes: f73f6dd312a5 ("drm/xe/pm: Add lockdep annotation for the pm_block completion")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202511061736.CiuroL7H-lkp@intel.com/
> Signed-off-by: Kriish Sharma <kriish.sharma2006@gmail.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
pushing soon to drm-xe-next
> ---
> drivers/gpu/drm/xe/xe_pm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
> index 7b089e6fb63f..44924512830f 100644
> --- a/drivers/gpu/drm/xe/xe_pm.c
> +++ b/drivers/gpu/drm/xe/xe_pm.c
> @@ -112,7 +112,7 @@ void xe_pm_might_block_on_suspend(void)
> }
>
> /**
> - * xe_pm_might_block_on_suspend() - Block pending suspend.
> + * xe_pm_block_on_suspend() - Block pending suspend.
> * @xe: The xe device about to be suspended.
> *
> * Block if the pm notifier has start evicting bos, to avoid
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-11-10 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 18:42 [PATCH] drm/xe: fix kernel-doc function name mismatch in xe_pm.c Kriish Sharma
2025-11-10 19:02 ` Rodrigo Vivi [this message]
2025-11-17 13:24 ` ✗ LGCI.VerificationFailed: failure for " 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=aRI2xnMDl2h4icmr@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=kriish.sharma2006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@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;
as well as URLs for NNTP newsgroup(s).