From: Guenter Roeck <linux@roeck-us.net>
To: Baole Ni <baolex.ni@intel.com>, jdelvare@suse.com
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0234/1285] Replace numeric parameter like 0444 with macro
Date: Tue, 2 Aug 2016 06:20:32 -0700 [thread overview]
Message-ID: <57A09E20.5080103@roeck-us.net> (raw)
In-Reply-To: <20160802105158.29348-1-baolex.ni@intel.com>
On 08/02/2016 03:51 AM, 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/abituguru.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/hwmon/abituguru.c b/drivers/hwmon/abituguru.c
> index 7a09c16..84d7070 100644
> --- a/drivers/hwmon/abituguru.c
> +++ b/drivers/hwmon/abituguru.c
> @@ -194,7 +194,7 @@ MODULE_PARM_DESC(pwms, "Number of PWMs on the uGuru "
>
> /* Default verbose is 2, since this driver is still in the testing phase */
> static int verbose = 2;
> -module_param(verbose, int, 0644);
> +module_param(verbose, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
S_IRUGO is quite useful, such as in "S_IRUGO | S_IWUSR".
Note that I cut down the excessive Cc:. Please don't do that again,
and please submit a single patch for the hwmon subsystem.
Guenter
prev parent reply other threads:[~2016-08-02 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 10:51 [PATCH 0234/1285] Replace numeric parameter like 0444 with macro Baole Ni
2016-08-02 13:20 ` Guenter Roeck [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=57A09E20.5080103@roeck-us.net \
--to=linux@roeck-us.net \
--cc=baolex.ni@intel.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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