From: Steven Rostedt <rostedt@goodmis.org>
To: Baole Ni <baolex.ni@intel.com>
Cc: paulmck@linux.vnet.ibm.com, josh@joshtriplett.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
m.chehab@samsung.com, gregkh@linuxfoundation.org,
m.szyprowski@samsung.com, kyungmin.park@samsung.com,
k.kozlowski@samsung.com, linux-kernel@vger.kernel.org,
chuansheng.liu@intel.com, mhocko@suse.com, tglx@linutronix.de,
vkuznets@redhat.com, pmladek@suse.com, tj@kernel.org,
jpoimboe@redhat.com
Subject: Re: [PATCH 1073/1285] Replace numeric parameter like 0444 with macro
Date: Tue, 2 Aug 2016 09:25:10 -0400 [thread overview]
Message-ID: <20160802092510.4d75a819@gandalf.local.home> (raw)
In-Reply-To: <20160802121358.21653-1-baolex.ni@intel.com>
On Tue, 2 Aug 2016 20:13:58 +0800
Baole Ni <baolex.ni@intel.com> wrote:
> I find that the developers often just specified the numeric value
> when calling a macro which is defined with a parameter for access permission.
> As we know, these numeric value for access permission have had the corresponding macro,
> and that using macro can improve the robustness and readability of the code,
> thus, I suggest replacing the numeric parameter with the macro.
>
NACK!
I find 0444 more readable than S_IRUSR | S_IRGRP | S_IROTH.
-- Steve
> Signed-off-by: Chuansheng Liu <chuansheng.liu@intel.com>
> Signed-off-by: Baole Ni <baolex.ni@intel.com>
> ---
> kernel/rcu/update.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/rcu/update.c b/kernel/rcu/update.c
> index 3e888cd..ee6df8e 100644
> --- a/kernel/rcu/update.c
> +++ b/kernel/rcu/update.c
> @@ -449,8 +449,8 @@ EXPORT_SYMBOL_GPL(do_trace_rcu_torture_read);
> int rcu_cpu_stall_suppress __read_mostly; /* 1 = suppress stall warnings. */
> static int rcu_cpu_stall_timeout __read_mostly = CONFIG_RCU_CPU_STALL_TIMEOUT;
>
> -module_param(rcu_cpu_stall_suppress, int, 0644);
> -module_param(rcu_cpu_stall_timeout, int, 0644);
> +module_param(rcu_cpu_stall_suppress, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
> +module_param(rcu_cpu_stall_timeout, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
>
> int rcu_jiffies_till_stall_check(void)
> {
> @@ -525,7 +525,7 @@ DEFINE_SRCU(tasks_rcu_exit_srcu);
>
> /* Control stall timeouts. Disable with <= 0, otherwise jiffies till stall. */
> static int rcu_task_stall_timeout __read_mostly = HZ * 60 * 10;
> -module_param(rcu_task_stall_timeout, int, 0644);
> +module_param(rcu_task_stall_timeout, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
>
> static void rcu_spawn_tasks_kthread(void);
>
> @@ -820,9 +820,9 @@ static bool rcu_self_test;
> static bool rcu_self_test_bh;
> static bool rcu_self_test_sched;
>
> -module_param(rcu_self_test, bool, 0444);
> -module_param(rcu_self_test_bh, bool, 0444);
> -module_param(rcu_self_test_sched, bool, 0444);
> +module_param(rcu_self_test, bool, S_IRUSR | S_IRGRP | S_IROTH);
> +module_param(rcu_self_test_bh, bool, S_IRUSR | S_IRGRP | S_IROTH);
> +module_param(rcu_self_test_sched, bool, S_IRUSR | S_IRGRP | S_IROTH);
>
> static int rcu_self_test_counter;
>
prev parent reply other threads:[~2016-08-02 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 12:13 Baole Ni
2016-08-02 13:25 ` Steven Rostedt [this message]
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=20160802092510.4d75a819@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=baolex.ni@intel.com \
--cc=chuansheng.liu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=jpoimboe@redhat.com \
--cc=k.kozlowski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=m.szyprowski@samsung.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhocko@suse.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pmladek@suse.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vkuznets@redhat.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 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®