mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Baole Ni <baolex.ni@intel.com>
Cc: tglx@linutronix.de, 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, vkuznets@redhat.com,
	pmladek@suse.com, tj@kernel.org, jpoimboe@redhat.com
Subject: Re: [PATCH 1074/1285] Replace numeric parameter like 0444 with macro
Date: Tue, 2 Aug 2016 09:25:26 -0400	[thread overview]
Message-ID: <20160802092526.60fe00c2@gandalf.local.home> (raw)
In-Reply-To: <20160802121404.21721-1-baolex.ni@intel.com>

On Tue,  2 Aug 2016 20:14:04 +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/time/clockevents.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/time/clockevents.c b/kernel/time/clockevents.c
> index a9b76a4..a0ff0f8 100644
> --- a/kernel/time/clockevents.c
> +++ b/kernel/time/clockevents.c
> @@ -667,7 +667,7 @@ static ssize_t sysfs_show_current_tick_dev(struct device *dev,
>  	raw_spin_unlock_irq(&clockevents_lock);
>  	return count;
>  }
> -static DEVICE_ATTR(current_device, 0444, sysfs_show_current_tick_dev, NULL);
> +static DEVICE_ATTR(current_device, S_IRUSR | S_IRGRP | S_IROTH, sysfs_show_current_tick_dev, NULL);
>  
>  /* We don't support the abomination of removable broadcast devices */
>  static ssize_t sysfs_unbind_tick_dev(struct device *dev,
> @@ -699,7 +699,7 @@ static ssize_t sysfs_unbind_tick_dev(struct device *dev,
>  	mutex_unlock(&clockevents_mutex);
>  	return ret ? ret : count;
>  }
> -static DEVICE_ATTR(unbind_device, 0200, NULL, sysfs_unbind_tick_dev);
> +static DEVICE_ATTR(unbind_device, S_IWUSR, NULL, sysfs_unbind_tick_dev);
>  
>  #ifdef CONFIG_GENERIC_CLOCKEVENTS_BROADCAST
>  static struct device tick_bc_dev = {

      reply	other threads:[~2016-08-02 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 12:14 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=20160802092526.60fe00c2@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=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®