From: Louis Chauvet <louis.chauvet@bootlin.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
thomas.petazzoni@bootlin.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] drm: writeback: Fix kernel doc name
Date: Thu, 20 Feb 2025 15:03:10 +0100 [thread overview]
Message-ID: <89b3f572-356a-4ccc-a55d-a4d15c6bee40@bootlin.com> (raw)
In-Reply-To: <xgkfvp7dmgzd64hriccbpyc2beoj7syiw2a5pgmtaao3fmlhdn@a5vudlyhzhqm>
Le 20/02/2025 à 14:49, Dmitry Baryshkov a écrit :
> On Thu, Feb 20, 2025 at 01:51:37PM +0100, Louis Chauvet wrote:
>>
>>
>> Le 07/02/2025 à 18:35, Louis Chauvet a écrit :
>>> During the creation of drmm_ variants for writeback connector, one
>>> function was renamed, but not the kernel doc.
>>>
>>> To remove the warning, use the proper name in kernel doc.
>>>
>>> Fixes: 135d8fc7af44 ("drm: writeback: Create an helper for drm_writeback_connector initialization")
>>> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
>>> Closes: https://lore.kernel.org/all/20250207142201.550ce870@canb.auug.org.au/
>>> Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.com>
>>
>> Hi all,
>>
>> Gentle ping on this patch. Can someone ack/review it so I can apply it on
>> drm-misc-next?
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Thanks,
Applied on drm-misc-next!
--
Louis Chauvet, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-02-20 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 17:35 Louis Chauvet
2025-02-08 4:58 ` Stephen Rothwell
2025-02-10 7:49 ` Maxime Ripard
2025-02-20 12:51 ` Louis Chauvet
2025-02-20 13:49 ` Dmitry Baryshkov
2025-02-20 14:03 ` Louis Chauvet [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=89b3f572-356a-4ccc-a55d-a4d15c6bee40@bootlin.com \
--to=louis.chauvet@bootlin.com \
--cc=airlied@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=simona@ffwll.ch \
--cc=thomas.petazzoni@bootlin.com \
--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
all inboxes | Powered by JetHome®