From: Varsha Rao <rvarsha016@gmail.com>
To: Matthew Wilcox <mawilcox@microsoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 1/5] drivers: char: Replace "foo * bar" with "foo *bar".
Date: Mon, 3 Apr 2017 21:38:57 +0530 [thread overview]
Message-ID: <58e2739d.9561630a.e3725.c55c@mx.google.com> (raw)
In-Reply-To: <cover.1491235332.git.rvarsha016@gmail.com>
Remove space after * in pointer type, to follow Linux coding style. This
patch fixes the following checkpatch issue:
ERROR: "foo * bar" should be "foo *bar"
Signed-off-by: Varsha Rao <rvarsha016@gmail.com>
---
drivers/char/misc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/char/misc.c b/drivers/char/misc.c
index 8069b36..ed8f79c 100644
--- a/drivers/char/misc.c
+++ b/drivers/char/misc.c
@@ -109,7 +109,7 @@ static const struct file_operations misc_proc_fops = {
};
#endif
-static int misc_open(struct inode * inode, struct file * file)
+static int misc_open(struct inode *inode, struct file *file)
{
int minor = iminor(inode);
struct miscdevice *c;
@@ -182,7 +182,7 @@ static const struct file_operations misc_fops = {
* failure.
*/
-int misc_register(struct miscdevice * misc)
+int misc_register(struct miscdevice *misc)
{
dev_t dev;
int err = 0;
--
2.9.3
next parent reply other threads:[~2017-04-03 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1491235332.git.rvarsha016@gmail.com>
2017-04-03 16:08 ` Varsha Rao [this message]
2017-04-03 16:09 ` [PATCH 2/5] drivers: char: Add space after ',' Varsha Rao
2017-04-03 16:11 ` [PATCH 3/5] drivers: char: Add blank line after declarations Varsha Rao
2017-04-03 16:11 ` [PATCH 4/5] drivers: char: Replace printk with pr_err Varsha Rao
2017-04-03 16:11 ` [PATCH 5/5] drivers: char: Replace bit operation functions with IDA allocator Varsha Rao
[not found] <cover.1491563538.git.rvarsha016@gmail.com>
2017-04-07 11:28 ` [PATCH 1/5] drivers: char: Replace "foo * bar" with "foo *bar" Varsha Rao
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=58e2739d.9561630a.e3725.c55c@mx.google.com \
--to=rvarsha016@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mawilcox@microsoft.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.