From: huzhi001@208suo.com
To: pmladek@suse.com, tglx@linutronix.de, senozhatsky@chromium.org,
adobriyan@gmail.com, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH] proc: Fix four errors in kmsg.c
Date: Fri, 14 Jul 2023 14:57:59 +0800 [thread overview]
Message-ID: <2f88487fa9f29eeb5a5bd4b6946a7e4c@208suo.com> (raw)
In-Reply-To: <tencent_053A1A860EFB7AAD92B2409B9D5AE06AB507@qq.com>
The following checkpatch errors are removed:
ERROR: "foo * bar" should be "foo *bar"
ERROR: "foo * bar" should be "foo *bar"
ERROR: "foo * bar" should be "foo *bar"
ERROR: "foo * bar" should be "foo *bar"
Signed-off-by: ZhiHu <huzhi001@208suo.com>
---
fs/proc/kmsg.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/proc/kmsg.c b/fs/proc/kmsg.c
index 2fc92a13f9f8..64025da60e2a 100644
--- a/fs/proc/kmsg.c
+++ b/fs/proc/kmsg.c
@@ -17,12 +17,12 @@
#include <asm/io.h>
-static int kmsg_open(struct inode * inode, struct file * file)
+static int kmsg_open(struct inode *inode, struct file *file)
{
return do_syslog(SYSLOG_ACTION_OPEN, NULL, 0, SYSLOG_FROM_PROC);
}
-static int kmsg_release(struct inode * inode, struct file * file)
+static int kmsg_release(struct inode *inode, struct file *file)
{
(void) do_syslog(SYSLOG_ACTION_CLOSE, NULL, 0, SYSLOG_FROM_PROC);
return 0;
next parent reply other threads:[~2023-07-14 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_053A1A860EFB7AAD92B2409B9D5AE06AB507@qq.com>
2023-07-14 6:57 ` huzhi001 [this message]
2023-07-14 8:22 ` [PATCH] proc: Fix four errors in kmsg.c Petr Mladek
2023-07-14 8:31 ` Petr Mladek
2023-07-17 6:05 ` Sergey Senozhatsky
2023-07-17 6:08 ` Randy Dunlap
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=2f88487fa9f29eeb5a5bd4b6946a7e4c@208suo.com \
--to=huzhi001@208suo.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
/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).