From: linmiaohe <linmiaohe@huawei.com>
To: "adobriyan@gmail.com" <adobriyan@gmail.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"dhowells@redhat.com" <dhowells@redhat.com>,
"cyphar@cyphar.com" <cyphar@cyphar.com>,
"christian@brauner.io" <christian@brauner.io>,
"aubrey.li@linux.intel.com" <aubrey.li@linux.intel.com>
Cc: Mingfangsen <mingfangsen@huawei.com>,
linmiaohe <linmiaohe@huawei.com>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] proc:fix confusing macro arg name
Date: Tue, 8 Oct 2019 06:44:18 +0000 [thread overview]
Message-ID: <165631b964b644dfa933653def533e41@huawei.com> (raw)
Add suitable additional cc's as Andrew Morton suggested.
Get cc list from get_maintainer script:
[root@localhost mm]# ./scripts/get_maintainer.pl 0001-proc-fix-confusing-macro-arg-name.patch
Alexey Dobriyan <adobriyan@gmail.com> (reviewer:PROC FILESYSTEM)
linux-kernel@vger.kernel.org (open list:PROC FILESYSTEM)
linux-fsdevel@vger.kernel.org (open list:PROC FILESYSTEM)
------------------------------------------------------
From: Miaohe Lin <linmiaohe@huawei.com>
Subject: fix confusing macro arg name
state_size and ops are in the wrong position, fix it.
Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/proc_fs.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/proc_fs.h b/include/linux/proc_fs.h index a705aa2d03f9..0640be56dcbd 100644
--- a/include/linux/proc_fs.h
+++ b/include/linux/proc_fs.h
@@ -58,8 +58,8 @@ extern int remove_proc_subtree(const char *, struct proc_dir_entry *); struct proc_dir_entry *proc_create_net_data(const char *name, umode_t mode,
struct proc_dir_entry *parent, const struct seq_operations *ops,
unsigned int state_size, void *data);
-#define proc_create_net(name, mode, parent, state_size, ops) \
- proc_create_net_data(name, mode, parent, state_size, ops, NULL)
+#define proc_create_net(name, mode, parent, ops, state_size) \
+ proc_create_net_data(name, mode, parent, ops, state_size, NULL)
struct proc_dir_entry *proc_create_net_single(const char *name, umode_t mode,
struct proc_dir_entry *parent,
int (*show)(struct seq_file *, void *), void *data);
--
2.21.GIT
next reply other threads:[~2019-10-08 6:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 6:44 linmiaohe [this message]
2019-10-08 7:04 ` Li, Aubrey
2019-10-08 7:27 ` Aleksa Sarai
2019-10-08 11:22 ` Christian Brauner
-- strict thread matches above, loose matches on Subject: below --
2019-10-08 8:28 linmiaohe
2019-09-10 2:17 Miaohe Lin
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=165631b964b644dfa933653def533e41@huawei.com \
--to=linmiaohe@huawei.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aubrey.li@linux.intel.com \
--cc=christian@brauner.io \
--cc=cyphar@cyphar.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingfangsen@huawei.com \
--cc=mm-commits@vger.kernel.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
Powered by JetHome