public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
	alexander.deucher@amd.com
Cc: Xinhui.Pan@amd.com, airlied@linux.ie, daniel@ffwll.ch,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amd/display: Clean up some inconsistent indenting
Date: Thu, 11 Nov 2021 11:08:50 +0100	[thread overview]
Message-ID: <abc4159c-e903-9265-826e-b44b387a7fcf@amd.com> (raw)
In-Reply-To: <1636625005-87952-1-git-send-email-jiapeng.chong@linux.alibaba.com>



Am 11.11.21 um 11:03 schrieb Jiapeng Chong:
> Eliminate the follow smatch warning:
>
> drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv.c:622
> dmub_srv_cmd_execute() warn: inconsistent indenting.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>

Reviewed-by: Christian König <christian.koenig@amd.com>

> ---
>   drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c b/drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c
> index 56a0332..e9fadf1 100644
> --- a/drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c
> +++ b/drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c
> @@ -618,8 +618,8 @@ enum dmub_status dmub_srv_cmd_execute(struct dmub_srv *dmub)
>   	 * read back stale, fully invalid or partially invalid data.
>   	 */
>   	dmub_rb_flush_pending(&dmub->inbox1_rb);
> +	dmub->hw_funcs.set_inbox1_wptr(dmub, dmub->inbox1_rb.wrpt);
>   
> -		dmub->hw_funcs.set_inbox1_wptr(dmub, dmub->inbox1_rb.wrpt);
>   	return DMUB_STATUS_OK;
>   }
>   


  reply	other threads:[~2021-11-11 10:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 10:03 [PATCH] drm/amd/display: Clean up some inconsistent indenting Jiapeng Chong
2021-11-11 10:08 ` Christian König [this message]
2021-11-12 22:55   ` Alex Deucher
  -- 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-03-22  3:14 [PATCH] drm/amd/display: Clean " Jiapeng Chong
2023-03-22 15:18 ` Hamza Mahfooz
2023-02-21  3:44 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  9:58 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=abc4159c-e903-9265-826e-b44b387a7fcf@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --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