From: liubin001@208suo.com
To: airlied@gmail.com, daniel@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Fwd: [PATCH] drm/vmwgfx: "foo* const bar" should be "foo * const bar"\ that ope- n brace { should be on the previous line
Date: Thu, 13 Jul 2023 11:11:18 +0800 [thread overview]
Message-ID: <7d2a5aba980cd6b7928c15e65fd94086@208suo.com> (raw)
In-Reply-To: <tencent_4F166AB6DC9C757B0454E3F4875027411F08@qq.com>
-------- 原始邮件 --------
主题:
[PATCH] drm/vmwgfx: "foo* const bar" should be "foo * const bar"\
that ope- n brace { should be on the previous line
日期:
2023-07-13 10:44
发件人:
fujie <2459483872@qq.com>
收件人:
liubin001@208suo.com
抄送:
fujie <2459483872@qq.com>
(1)The standard format for declaring a pointer is to add a space bet-
ween the type name and the * symbol, as well as between the * symbol and
the variable name.
(2) that open brace { should be on the previous line
Signed-off-by: fujie <2459483872@qq.com>
---
drivers/gpu/drm/vmwgfx/vmwgfx_msg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_msg.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_msg.c
index 96504a320c2a..b56936f95d31 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_msg.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_msg.c
@@ -87,7 +87,7 @@ struct rpc_channel {
#if IS_ENABLED(CONFIG_DRM_VMWGFX_MKSSTATS)
/* Kernel mksGuestStats counter names and desciptions; same order as
enum mksstat_kern_stats_t */
-static const char* const mksstat_kern_name_desc[MKSSTAT_KERN_COUNT][2]
=
{
{ "vmw_execbuf_ioctl", "vmw_execbuf_ioctl" },
{ "vmw_cotable_resize", "vmw_cotable_resize" },
};
+static const char * const mksstat_kern_name_desc[MKSSTAT_KERN_COUNT][2]
= {
{ "vmw_execbuf_ioctl", "vmw_execbuf_ioctl" },
{ "vmw_cotable_resize", "vmw_cotable_resize" },
};
WARNING: multiple messages have this Message-ID
From: liubin001@208suo.com
To: airlied@gmail.com, daniel@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH] drm/vmwgfx: "foo* const bar" should be "foo * const bar"\ that ope- n brace { should be on the previous line
Date: Thu, 13 Jul 2023 11:17:29 +0800 [thread overview]
Message-ID: <7d2a5aba980cd6b7928c15e65fd94086@208suo.com> (raw)
Message-ID: <20230713031729.uJJZC_Yu1OO_rjklzagJiodicDBP6xr4_jhwiqb86Xc@z> (raw)
In-Reply-To: <tencent_4F166AB6DC9C757B0454E3F4875027411F08@qq.com>
(1)The standard format for declaring a pointer is to add a space bet-
ween the type name and the * symbol, as well as between the * symbol and
the variable name.
(2) that open brace { should be on the previous line
Signed-off-by: Bin Liu <liubin001@208suo.com>
---
drivers/gpu/drm/vmwgfx/vmwgfx_msg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_msg.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_msg.c
index 96504a320c2a..b56936f95d31 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_msg.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_msg.c
@@ -87,7 +87,7 @@ struct rpc_channel {
#if IS_ENABLED(CONFIG_DRM_VMWGFX_MKSSTATS)
/* Kernel mksGuestStats counter names and desciptions; same order as
enum mksstat_kern_stats_t */
-static const char* const mksstat_kern_name_desc[MKSSTAT_KERN_COUNT][2]
=
{
{ "vmw_execbuf_ioctl", "vmw_execbuf_ioctl" },
{ "vmw_cotable_resize", "vmw_cotable_resize" },
};
+static const char * const mksstat_kern_name_desc[MKSSTAT_KERN_COUNT][2]
= {
{ "vmw_execbuf_ioctl", "vmw_execbuf_ioctl" },
{ "vmw_cotable_resize", "vmw_cotable_resize" },
};
next parent reply other threads:[~2023-07-13 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_4F166AB6DC9C757B0454E3F4875027411F08@qq.com>
2023-07-13 3:11 ` liubin001 [this message]
2023-07-13 3:17 ` liubin001
2023-07-13 3:15 ` Fwd: " liubin001
2023-07-13 3:19 ` liubin001
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=7d2a5aba980cd6b7928c15e65fd94086@208suo.com \
--to=liubin001@208suo.com \
--cc=airlied@gmail.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®