public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Stylon Wang <stylon.wang@amd.com>
To: <stable@vger.kernel.org>
Cc: <stylon.wang@amd.com>, <jude.shih@amd.com>,
	Yann Dirson <ydirson@free.fr>,
	Alex Deucher <alexander.deucher@amd.com>,
	kernel test robot <lkp@intel.com>
Subject: [PATCH] amdgpu: fix some kernel-doc markup
Date: Mon, 22 May 2023 20:04:13 +0800	[thread overview]
Message-ID: <20230522120413.2931343-1-stylon.wang@amd.com> (raw)

From: Yann Dirson <ydirson@free.fr>

commit 03f2abb07e54b3e0da54c52a656d9765b7e141c5 upstream.

Those are not today pulled by the sphinx doc, but better be ready.

Two lines of the cherry-picked patch is removed because they are being
refactored away from this file:
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h

Signed-off-by: Yann Dirson <ydirson@free.fr>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Reported-by: kernel test robot <lkp@intel.com>
Link: https://lore.kernel.org/oe-kbuild-all/202302281017.9qcgLAZi-lkp@intel.com/
Cc: <stable@vger.kernel.org> # 5.15.x
(cherry picked from commit 03f2abb07e54b3e0da54c52a656d9765b7e141c5)
---
 drivers/gpu/drm/amd/amdgpu/amdgpu_device.c        | 6 +++---
 drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
index b0d9c47cc381..a5cf672e79c5 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
@@ -557,11 +557,11 @@ void amdgpu_device_wreg(struct amdgpu_device *adev,
 	trace_amdgpu_device_wreg(adev->pdev->device, reg, v);
 }
 
-/*
+/**
  * amdgpu_mm_wreg_mmio_rlc -  write register either with mmio or with RLC path if in range
  *
  * this function is invoked only the debugfs register access
- * */
+ */
 void amdgpu_mm_wreg_mmio_rlc(struct amdgpu_device *adev,
 			     uint32_t reg, uint32_t v)
 {
@@ -1107,7 +1107,7 @@ static void amdgpu_device_wb_fini(struct amdgpu_device *adev)
 }
 
 /**
- * amdgpu_device_wb_init- Init Writeback driver info and allocate memory
+ * amdgpu_device_wb_init - Init Writeback driver info and allocate memory
  *
  * @adev: amdgpu_device pointer
  *
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
index fa4f0a205127..81d033b99591 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
@@ -622,7 +622,7 @@ static void dm_dcn_vertical_interrupt0_high_irq(void *interrupt_params)
 #endif
 
 /**
- * dmub_aux_setconfig_reply_callback - Callback for AUX or SET_CONFIG command.
+ * dmub_aux_setconfig_callback - Callback for AUX or SET_CONFIG command.
  * @adev: amdgpu_device pointer
  * @notify: dmub notification structure
  *
-- 
2.40.0


             reply	other threads:[~2023-05-22 12:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 12:04 Stylon Wang [this message]
2023-05-22 18:41 ` [PATCH] amdgpu: fix some kernel-doc markup Greg KH
     [not found]   ` <BN9PR12MB5145A7D7D53F2572A546039DFF409@BN9PR12MB5145.namprd12.prod.outlook.com>
2023-05-23  6:03     ` Philip Li

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=20230522120413.2931343-1-stylon.wang@amd.com \
    --to=stylon.wang@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=jude.shih@amd.com \
    --cc=lkp@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=ydirson@free.fr \
    /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