From: neil.armstrong@linaro.org
To: Dongyang Jin <jindongyang@kylinos.cn>,
jesszhan0024@gmail.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] drm/panel: fix kernel-doc warning for devm_drm_panel_add()
Date: Thu, 21 May 2026 15:05:49 +0200 [thread overview]
Message-ID: <88c5e061-ebad-4f97-be93-a2b6bca75041@linaro.org> (raw)
In-Reply-To: <20260521094545.3039207-1-jindongyang@kylinos.cn>
On 5/21/26 11:45, Dongyang Jin wrote:
> Use the correct kernel-doc notation for struct members to eliminate
> kernel-doc warnings:
>
> Warning: drivers/gpu/drm/drm_panel.c:119 function parameter 'dev'
> not described in 'devm_drm_panel_add'
> Warning: drivers/gpu/drm/drm_panel.c:119 function parameter 'dev'
> not described in 'devm_drm_panel_add'
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202605210648.RI4ufD66-lkp@intel.com/
> Signed-off-by: Dongyang Jin <jindongyang@kylinos.cn>
> ---
> drivers/gpu/drm/drm_panel.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/drm_panel.c b/drivers/gpu/drm/drm_panel.c
> index 04f4a31ed27a..2c5649e433df 100644
> --- a/drivers/gpu/drm/drm_panel.c
> +++ b/drivers/gpu/drm/drm_panel.c
> @@ -108,6 +108,7 @@ static void drm_panel_add_release(void *data)
>
> /**
> * devm_drm_panel_add - add a panel to the global registry using devres
> + * @dev: device to which the panel is attached
> * @panel: panel to add
> *
> * Add a panel to the global registry so that it can be looked
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Thanks,
Neil
next prev parent reply other threads:[~2026-05-21 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 9:45 [PATCH] drm/panel: fix kernel-doc warning for devm_drm_panel_add() Dongyang Jin
2026-05-21 13:05 ` neil.armstrong [this message]
2026-05-25 10:23 ` Claude review: " Claude Code Review Bot
2026-05-25 10:23 ` Claude Code Review Bot
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=88c5e061-ebad-4f97-be93-a2b6bca75041@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=jindongyang@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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