From: Matt Jan <zoo868e@gmail.com>
To: Martyn Welch <martyn@welchs.me.uk>,
Manohar Vanga <manohar.vanga@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Cc: Matt Jan <zoo868e@gmail.com>
Subject: [PATCH v3 1/3] staging: vme_user: add the spaces around the "*"
Date: Fri, 9 Dec 2022 10:17:54 +0800 [thread overview]
Message-ID: <20221209021756.5597-1-zoo868e@gmail.com> (raw)
Add a space around the "*" at vme_bridge.h to clear up a checkpatch
check.
Signed-off-by: Matt Jan <zoo868e@gmail.com>
---
Changelog
v2->v3: Resend the patch set in properly threaded and move the patch
changelog to correct position, noted by Greg Kroah-Hartman
<gregkh@linuxfoundation.org>
v1->v2: Resend the correct patch set, noted by Greg Kroah-Hartman
<gregkh@linuxfoundation.org>
drivers/staging/vme_user/vme_bridge.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/vme_user/vme_bridge.h b/drivers/staging/vme_user/vme_bridge.h
index 0bbefe9851d7..e17a8f7de165 100644
--- a/drivers/staging/vme_user/vme_bridge.h
+++ b/drivers/staging/vme_user/vme_bridge.h
@@ -4,7 +4,7 @@
#include "vme.h"
-#define VME_CRCSR_BUF_SIZE (508*1024)
+#define VME_CRCSR_BUF_SIZE (508 * 1024)
/*
* Resource structures
*/
--
2.25.1
next reply other threads:[~2022-12-09 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 2:17 Matt Jan [this message]
2022-12-09 2:17 ` [PATCH v3 2/3] staging: vme_user: remove unnecessary spaces Matt Jan
2022-12-09 2:17 ` [PATCH v3 3/3] staging: vme_user: replace 'unsigned' with 'unsigned int' Matt Jan
[not found] <20221208140531.3840-1-zoo868e@gmail.com>
2022-12-08 16:01 ` [PATCH v3 1/3] staging: vme_user: add the spaces around the "*" Greg Kroah-Hartman
[not found] ` <CAB9pA+-2tZQDXxQ4JPrXb6K0HH=gv_9SAPKp1DSrk_M6OxL06g@mail.gmail.com>
2022-12-08 18:20 ` Greg Kroah-Hartman
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=20221209021756.5597-1-zoo868e@gmail.com \
--to=zoo868e@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manohar.vanga@gmail.com \
--cc=martyn@welchs.me.uk \
/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®