From: Mario Limonciello <mario.limonciello@amd.com>
To: Kevin Paul Reddy Janagari <kevinpaul468@gmail.com>,
alexander.deucher@amd.com, christian.koenig@amd.com,
airlied@gmail.com, simona@ffwll.ch, sunil.khatri@amd.com,
aurabindo.pillai@amd.com, boyuan.zhang@amd.com,
sunpeng.li@amd.com, dominik.kaszewski@amd.com
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org
Subject: Re: [PATCH] Fixed the warning at ./drivers/gpu/drm/amd/include/amd_shared.h:369
Date: Tue, 8 Apr 2025 15:29:40 -0500 [thread overview]
Message-ID: <0b65112c-3de8-44c9-ae40-96bad5daddaf@amd.com> (raw)
In-Reply-To: <20250405031242.64373-1-kevinpaul468@gmail.com>
On 4/4/2025 10:12 PM, Kevin Paul Reddy Janagari wrote:
> warning: Incorrect use of kernel-doc format:
> * @DC_HDCP_LC_ENABLE_SW_FALLBACK If set, upon HDCP Locality Check FW
>
> Signed-off-by: Kevin Paul Reddy Janagari <kevinpaul468@gmail.com>
> ---
> drivers/gpu/drm/amd/include/amd_shared.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/include/amd_shared.h b/drivers/gpu/drm/amd/include/amd_shared.h
> index 4c95b885d1d0..c8eccee9b023 100644
> --- a/drivers/gpu/drm/amd/include/amd_shared.h
> +++ b/drivers/gpu/drm/amd/include/amd_shared.h
> @@ -366,7 +366,7 @@ enum DC_DEBUG_MASK {
> DC_HDCP_LC_FORCE_FW_ENABLE = 0x80000,
>
> /**
> - * @DC_HDCP_LC_ENABLE_SW_FALLBACK If set, upon HDCP Locality Check FW
> + * @DC_HDCP_LC_ENABLE_SW_FALLBACK: If set, upon HDCP Locality Check FW
> * path failure, retry using legacy SW path.
> */
> DC_HDCP_LC_ENABLE_SW_FALLBACK = 0x100000,
Thanks for the patch! But FWIW this was already fixed in this patch
which is on amd-staging-drm-next now.
https://lore.kernel.org/amd-gfx/20250319111243.14206-1-dominik.kaszewski@amd.com/
prev parent reply other threads:[~2025-04-08 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 3:12 [PATCH] Fixed the warning at ./drivers/gpu/drm/amd/include/amd_shared.h:369 Kevin Paul Reddy Janagari
2025-04-08 20:29 ` Mario Limonciello [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=0b65112c-3de8-44c9-ae40-96bad5daddaf@amd.com \
--to=mario.limonciello@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aurabindo.pillai@amd.com \
--cc=boyuan.zhang@amd.com \
--cc=christian.koenig@amd.com \
--cc=dominik.kaszewski@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kevinpaul468@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=sunil.khatri@amd.com \
--cc=sunpeng.li@amd.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