From: Yang Yingliang <yangyingliang@huawei.com>
To: <linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>
Cc: alexander.deucher@amd.com, christian.koenig@amd.com
Subject: [PATCH -next 3/4] drm/radeon/r100: correct function name r100_cs_packet_parse_vline()
Date: Thu, 13 May 2021 15:25:58 +0800 [thread overview]
Message-ID: <20210513072559.1731410-4-yangyingliang@huawei.com> (raw)
In-Reply-To: <20210513072559.1731410-1-yangyingliang@huawei.com>
Fix the following make W=1 kernel build warning:
drivers/gpu/drm/radeon/r100.c:1423: warning: expecting prototype for r100_cs_packet_next_vline(). Prototype was for r100_cs_packet_parse_vline() instead
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
drivers/gpu/drm/radeon/r100.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/radeon/r100.c b/drivers/gpu/drm/radeon/r100.c
index fcfcaec25a9e..3c4e7c15fd15 100644
--- a/drivers/gpu/drm/radeon/r100.c
+++ b/drivers/gpu/drm/radeon/r100.c
@@ -1406,7 +1406,7 @@ int r100_cs_parse_packet0(struct radeon_cs_parser *p,
}
/**
- * r100_cs_packet_next_vline() - parse userspace VLINE packet
+ * r100_cs_packet_parse_vline() - parse userspace VLINE packet
* @p: parser structure holding parsing context.
*
* Userspace sends a special sequence for VLINE waits.
--
2.25.1
next prev parent reply other threads:[~2021-05-13 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 7:25 [PATCH -next 0/4] drm/radeon: fix some doc-warnings Yang Yingliang
2021-05-13 7:25 ` [PATCH -next 1/4] drm/radeon/cik: correct function name cik_irq_suspend() Yang Yingliang
2021-05-13 7:25 ` [PATCH -next 2/4] drm/radeon: correct function name radeon_cs_parser_fini() Yang Yingliang
2021-05-13 7:25 ` Yang Yingliang [this message]
2021-05-13 7:25 ` [PATCH -next 4/4] drm/radeon/radeon_vm: correct function names in radeon_vm.c Yang Yingliang
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=20210513072559.1731410-4-yangyingliang@huawei.com \
--to=yangyingliang@huawei.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--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;
as well as URLs for NNTP newsgroup(s).