public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Baole Ni <baolex.ni@intel.com>
Cc: jdelvare@suse.com, linux@roeck-us.net, airlied@linux.ie,
	kgene@kernel.org, k.kozlowski@samsung.com,
	dougthompson@xmission.com, bp@alien8.de,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
	chuansheng.liu@intel.com, aduggan@synaptics.com,
	dianders@chromium.org
Subject: Re: [PATCH 0239/1285] Replace numeric parameter like 0444 with macro
Date: Tue, 2 Aug 2016 14:22:13 +0200	[thread overview]
Message-ID: <20160802122213.GA23544@kroah.com> (raw)
In-Reply-To: <20160802105221.29678-1-baolex.ni@intel.com>

On Tue, Aug 02, 2016 at 06:52:21PM +0800, Baole Ni 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.
> 
> Signed-off-by: Chuansheng Liu <chuansheng.liu@intel.com>
> Signed-off-by: Baole Ni <baolex.ni@intel.com>
> ---
>  drivers/hwmon/fschmd.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/hwmon/fschmd.c b/drivers/hwmon/fschmd.c
> index d58abdc..a7e4885 100644
> --- a/drivers/hwmon/fschmd.c
> +++ b/drivers/hwmon/fschmd.c
> @@ -602,7 +602,7 @@ static ssize_t store_alert_led(struct device *dev,
>  	return count;
>  }
>  
> -static DEVICE_ATTR(alert_led, 0644, show_alert_led, store_alert_led);
> +static DEVICE_ATTR(alert_led, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH, show_alert_led, store_alert_led);

Use DEVICE_ATTR_RW() please.

      reply	other threads:[~2016-08-02 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 10:52 [PATCH 0239/1285] Replace numeric parameter like 0444 with macro Baole Ni
2016-08-02 12:22 ` Greg KH [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=20160802122213.GA23544@kroah.com \
    --to=greg@kroah.com \
    --cc=aduggan@synaptics.com \
    --cc=airlied@linux.ie \
    --cc=baolex.ni@intel.com \
    --cc=bp@alien8.de \
    --cc=chuansheng.liu@intel.com \
    --cc=dianders@chromium.org \
    --cc=dougthompson@xmission.com \
    --cc=jdelvare@suse.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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