mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: shijie001@208suo.com
To: airlied@gmail.com, daniel@ffwll.ch, christian.koenig@amd.com,
	alexander.deucher@amd.com, Xinhui.Pan@amd.com
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH] drm/radeon: ERROR: open brace '{' following function definitions go on the next line
Date: Fri, 14 Jul 2023 11:20:47 +0800	[thread overview]
Message-ID: <50bf0cff1b048f24484f32ff0e5015f6@208suo.com> (raw)
In-Reply-To: <tencent_21616D4FB2F221FE67B71858B197C646AB08@qq.com>

Fix four occurrences of the checkpatch.pl error:
ERROR: open brace '{' following function definitions go on the next line

Signed-off-by: Jie Shi <shijie001@208suo.com>
---
  drivers/gpu/drm/radeon/radeon_atpx_handler.c | 12 ++++++++----
  1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/drivers/gpu/drm/radeon/radeon_atpx_handler.c 
b/drivers/gpu/drm/radeon/radeon_atpx_handler.c
index 6f93f54bf651..2a3c3f8b02e2 100644
--- a/drivers/gpu/drm/radeon/radeon_atpx_handler.c
+++ b/drivers/gpu/drm/radeon/radeon_atpx_handler.c
@@ -61,19 +61,23 @@ struct atpx_mux {
      u16 mux;
  } __packed;

-bool radeon_has_atpx(void) {
+bool radeon_has_atpx(void)
+{
      return radeon_atpx_priv.atpx_detected;
  }

-bool radeon_has_atpx_dgpu_power_cntl(void) {
+bool radeon_has_atpx_dgpu_power_cntl(void)
+{
      return radeon_atpx_priv.atpx.functions.power_cntl;
  }

-bool radeon_is_atpx_hybrid(void) {
+bool radeon_is_atpx_hybrid(void)
+{
      return radeon_atpx_priv.atpx.is_hybrid;
  }

-bool radeon_atpx_dgpu_req_power_for_displays(void) {
+bool radeon_atpx_dgpu_req_power_for_displays(void)
+{
      return radeon_atpx_priv.atpx.dgpu_req_power_for_displays;
  }

           reply	other threads:[~2023-07-14  3:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <tencent_21616D4FB2F221FE67B71858B197C646AB08@qq.com>]

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=50bf0cff1b048f24484f32ff0e5015f6@208suo.com \
    --to=shijie001@208suo.com \
    --cc=Xinhui.Pan@amd.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=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

all inboxes | Powered by JetHome®