From: Alex Deucher <alexdeucher@gmail.com>
To: sunran001@208suo.com
Cc: alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amd/pm: Clean up errors in smu_v13_0_1_pmfw.h
Date: Mon, 24 Jul 2023 17:58:25 -0400 [thread overview]
Message-ID: <CADnq5_Pj+B8azBwSMAWg5d=UWS9ey-wnVTJWLScHCv--xMLTgw@mail.gmail.com> (raw)
In-Reply-To: <7e638628f942fe7989fe2da3da537c28@208suo.com>
This doesn't apply cleanly.
Alex
On Mon, Jul 24, 2023 at 4:57 AM <sunran001@208suo.com> wrote:
>
> Fix the following errors reported by checkpatch:
>
> ERROR: trailing whitespace
>
> Signed-off-by: Ran Sun <sunran001@208suo.com>
> ---
> drivers/gpu/drm/amd/pm/swsmu/inc/pmfw_if/smu_v13_0_1_pmfw.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/pm/swsmu/inc/pmfw_if/smu_v13_0_1_pmfw.h
> b/drivers/gpu/drm/amd/pm/swsmu/inc/pmfw_if/smu_v13_0_1_pmfw.h
> index c5e26d619bf0..8ec588248aac 100644
> --- a/drivers/gpu/drm/amd/pm/swsmu/inc/pmfw_if/smu_v13_0_1_pmfw.h
> +++ b/drivers/gpu/drm/amd/pm/swsmu/inc/pmfw_if/smu_v13_0_1_pmfw.h
> @@ -30,7 +30,7 @@
>
> #define ENABLE_DEBUG_FEATURES
>
> -// Firmware features
> +// Firmware features
> // Feature Control Defines
> #define FEATURE_CCLK_DPM_BIT 0
> #define FEATURE_FAN_CONTROLLER_BIT 1
> @@ -92,7 +92,7 @@
> #define FEATURE_ZSTATES_ECO_BIT 57
> #define FEATURE_CC6_BIT 58
> #define FEATURE_DS_UMCCLK_BIT 59
> -#define FEATURE_DS_HSPCLK_BIT 60
> +#define FEATURE_DS_HSPCLK_BIT 60
> #define NUM_FEATURES 61
>
> typedef struct {
prev parent reply other threads:[~2023-07-24 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230724083344.9285-1-xujianghui@cdjrlc.com>
2023-07-24 8:34 ` [PATCH] drm/amd/pm: Clean up errors in smu11_driver_if_sienna_cichlid.h sunran001
2023-07-24 21:52 ` Alex Deucher
2023-07-24 8:57 ` [PATCH] drm/amd/pm: Clean up errors in smu_v13_0_1_pmfw.h sunran001
2023-07-24 21:58 ` Alex Deucher [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='CADnq5_Pj+B8azBwSMAWg5d=UWS9ey-wnVTJWLScHCv--xMLTgw@mail.gmail.com' \
--to=alexdeucher@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sunran001@208suo.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).