From: "Christian König" <christian.koenig@amd.com>
To: Sunil Khatri <sunil.khatri@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Boyuan Zhang <boyuan.zhang@amd.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: fix html doc generation warning
Date: Wed, 2 Oct 2024 11:32:20 +0200 [thread overview]
Message-ID: <4e5bfd0f-0ea3-4e15-80ff-593503e62f70@amd.com> (raw)
In-Reply-To: <20241002092618.116982-1-sunil.khatri@amd.com>
Am 02.10.24 um 11:26 schrieb Sunil Khatri:
> Fix the html doc warning due to mix up of the
> forward declaration of struct amdgpu_ip_block.
>
> Signed-off-by: Sunil Khatri <sunil.khatri@amd.com>
> ---
> drivers/gpu/drm/amd/include/amd_shared.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/include/amd_shared.h b/drivers/gpu/drm/amd/include/amd_shared.h
> index d892273fdb10..f98b3a544477 100644
> --- a/drivers/gpu/drm/amd/include/amd_shared.h
> +++ b/drivers/gpu/drm/amd/include/amd_shared.h
> @@ -28,6 +28,8 @@
>
>
> #define AMD_MAX_USEC_TIMEOUT 1000000 /* 1000 ms */
> +struct amdgpu_ip_block;
> +
Not a most have but probably best to add an empty line between the
#define and the forward declaration.
Reviewed-by: Christian König <christian.koenig@amd.com> either way.
>
> /*
> * Chip flags
> @@ -375,8 +377,6 @@ enum amd_dpm_forced_level;
> * making calls to hooks from each IP block. This list is ordered to ensure
> * that the driver initializes the IP blocks in a safe sequence.
> */
> -struct amdgpu_ip_block;
> -
> struct amd_ip_funcs {
> char *name;
> int (*early_init)(struct amdgpu_ip_block *ip_block);
prev parent reply other threads:[~2024-10-02 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 9:26 [PATCH] drm/amdgpu: fix html doc generation warning Sunil Khatri
2024-10-02 9:32 ` Christian König [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=4e5bfd0f-0ea3-4e15-80ff-593503e62f70@amd.com \
--to=christian.koenig@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=boyuan.zhang@amd.com \
--cc=sunil.khatri@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