From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Baole Ni <baolex.ni@intel.com>,
b.zolnierkie@samsung.com, tj@kernel.org, lenb@kernel.org,
x86@kernel.org, hpa@zytor.com
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
chuansheng.liu@intel.com, travis@sgi.com
Subject: Re: [PATCH 0063/1285] Replace numeric parameter like 0444 with macro
Date: Tue, 2 Aug 2016 15:32:57 +0300 [thread overview]
Message-ID: <a4bf3836-1ffa-9f83-6e8f-998c99d5b507@cogentembedded.com> (raw)
In-Reply-To: <5391e340-1285-574d-1979-a19571341eb5@cogentembedded.com>
Hello.
On 8/2/2016 2:30 PM, Sergei Shtylyov 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/ata/pata_legacy.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/ata/pata_legacy.c b/drivers/ata/pata_legacy.c
>> index bce2a8c..1dc0beb 100644
>> --- a/drivers/ata/pata_legacy.c
>> +++ b/drivers/ata/pata_legacy.c
>> @@ -76,7 +76,7 @@
>> #define NR_HOST 6
>>
>> static int all;
>> -module_param(all, int, 0444);
>> +module_param(all, int, S_IRUSR | S_IRGRP | S_IROTH);
>
> There's S_IRUGO for this case, no?
Sending 1285 patches with the same subject also was a bad idea. You need a
subsystem/driver prefix in order to somehow differ them.
MBR, Sergei
next prev parent reply other threads:[~2016-08-02 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 10:37 Baole Ni
2016-08-02 11:30 ` Sergei Shtylyov
2016-08-02 12:32 ` Sergei Shtylyov [this message]
2016-08-02 13:19 ` Steven Rostedt
2016-08-02 13:58 ` Marcel Holtmann
2016-08-02 18:27 ` Tejun Heo
2016-08-02 18:32 ` David Miller
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=a4bf3836-1ffa-9f83-6e8f-998c99d5b507@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=b.zolnierkie@samsung.com \
--cc=baolex.ni@intel.com \
--cc=chuansheng.liu@intel.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=travis@sgi.com \
--cc=x86@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
all inboxes | Powered by JetHome®