[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1470156329.16559.57.camel@infradead.org>
Date: Tue, 02 Aug 2016 09:45:29 -0700
From: Geoff Levand <geoff@...radead.org>
To: Baole Ni <baolex.ni@...el.com>, benh@...nel.crashing.org,
paulus@...ba.org, mpe@...erman.id.au, dwmw2@...radead.org,
m.chehab@...sung.com, pawel@...iak.com, m.szyprowski@...sung.com,
kyungmin.park@...sung.com, k.kozlowski@...sung.com
Cc: linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
chuansheng.liu@...el.com
Subject: Re: [PATCH 0867/1285] Replace numeric parameter like 0444 with macro
On Tue, 2016-08-02 at 19:53 +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@...el.com>
> Signed-off-by: Baole Ni <baolex.ni@...el.com>
> ---
>
> static int timeout = 5000; /* in msec ( 5 sec ) */
> -module_param(timeout, int, 0644);
> +module_param(timeout, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
To me, 644 is more 'readable', and as for robustness, the meaning of
644 will never change.
-Geoff
Powered by blists - more mailing lists