From: Hamza Mahfooz <hamza.mahfooz@amd.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
alexander.deucher@amd.com
Cc: Xinhui.Pan@amd.com, Abaci Robot <abaci@linux.alibaba.com>,
linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, daniel@ffwll.ch,
airlied@gmail.com, christian.koenig@amd.com
Subject: Re: [PATCH] drm/amd/display: Clean up some inconsistent indenting
Date: Wed, 22 Mar 2023 11:18:55 -0400 [thread overview]
Message-ID: <f9505055-7e5d-e217-d81f-eae0de5afdcf@amd.com> (raw)
In-Reply-To: <20230322031419.98509-1-jiapeng.chong@linux.alibaba.com>
On 3/21/23 23:14, Jiapeng Chong wrote:
> No functional modification involved.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=4585
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Applied, thanks!
> ---
> drivers/gpu/drm/amd/display/modules/power/power_helpers.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/display/modules/power/power_helpers.c b/drivers/gpu/drm/amd/display/modules/power/power_helpers.c
> index fa469de3e935..0d3a983cb9ec 100644
> --- a/drivers/gpu/drm/amd/display/modules/power/power_helpers.c
> +++ b/drivers/gpu/drm/amd/display/modules/power/power_helpers.c
> @@ -758,8 +758,8 @@ bool dmcu_load_iram(struct dmcu *dmcu,
>
> if (dmcu->dmcu_version.abm_version == 0x24) {
> fill_iram_v_2_3((struct iram_table_v_2_2 *)ram_table, params, true);
> - result = dmcu->funcs->load_iram(
> - dmcu, 0, (char *)(&ram_table), IRAM_RESERVE_AREA_START_V2_2);
> + result = dmcu->funcs->load_iram(dmcu, 0, (char *)(&ram_table),
> + IRAM_RESERVE_AREA_START_V2_2);
> } else if (dmcu->dmcu_version.abm_version == 0x23) {
> fill_iram_v_2_3((struct iram_table_v_2_2 *)ram_table, params, true);
>
--
Hamza
next prev parent reply other threads:[~2023-03-22 15:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 3:14 [PATCH] drm/amd/display: Clean up some inconsistent indenting Jiapeng Chong
2023-03-22 15:18 ` Hamza Mahfooz [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-06 9:44 [PATCH] drm/amd/display: clean " Jiapeng Chong
2024-05-24 2:19 Jiapeng Chong
2024-05-24 13:44 ` Alex Deucher
2024-05-11 2:43 Jiapeng Chong
2024-03-22 6:08 Jiapeng Chong
2023-11-17 6:40 Jiapeng Chong
2023-11-10 7:44 Jiapeng Chong
2023-10-19 3:38 Jiapeng Chong
2023-10-19 14:51 ` Alex Deucher
2023-09-08 7:54 Jiapeng Chong
2023-09-11 16:20 ` Hamza Mahfooz
2023-06-02 6:17 Jiapeng Chong
2023-06-02 13:16 ` Alex Deucher
2023-06-02 14:28 ` Hamza Mahfooz
2023-02-21 3:44 [PATCH] drm/amd/display: Clean " Jiapeng Chong
2023-02-23 13:49 ` Alex Deucher
2022-05-12 7:19 [PATCH] drm/amd/display: clean " Jiapeng Chong
2022-05-13 16:57 ` Alex Deucher
2021-11-11 10:03 [PATCH] drm/amd/display: Clean " Jiapeng Chong
2021-11-11 10:08 ` Christian König
2021-11-12 22:55 ` Alex Deucher
2021-11-11 9:58 [PATCH] drm/amd/display: clean " Jiapeng Chong
2021-11-11 10:08 ` Christian König
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=f9505055-7e5d-e217-d81f-eae0de5afdcf@amd.com \
--to=hamza.mahfooz@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=abaci@linux.alibaba.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
/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