netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 0746/1285] Replace numeric parameter like 0444 with macro
@ 2016-08-02 11:42 Baole Ni
  2016-08-02 12:32 ` Jiri Benc
  0 siblings, 1 reply; 2+ messages in thread
From: Baole Ni @ 2016-08-02 11:42 UTC (permalink / raw)
  To: michal.simek, soren.brinkmann, bkenward, linux-driver,
	computersforpeace, m.chehab, pawel, m.szyprowski, kyungmin.park,
	k.kozlowski
  Cc: netdev, linux-kernel, davem, jesse, linville, pshelar, jbenc,
	daniel, hannes, tom, aduyck, chuansheng.liu, baolex.ni

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/net/geneve.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/geneve.c b/drivers/net/geneve.c
index cadefe4..2ddaa09 100644
--- a/drivers/net/geneve.c
+++ b/drivers/net/geneve.c
@@ -32,7 +32,7 @@
 #define VNI_HASH_SIZE		(1<<VNI_HASH_BITS)
 
 static bool log_ecn_error = true;
-module_param(log_ecn_error, bool, 0644);
+module_param(log_ecn_error, bool, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
 MODULE_PARM_DESC(log_ecn_error, "Log packets received with corrupted ECN");
 
 #define GENEVE_VER 0
-- 
2.9.2

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH 0746/1285] Replace numeric parameter like 0444 with macro
  2016-08-02 11:42 [PATCH 0746/1285] Replace numeric parameter like 0444 with macro Baole Ni
@ 2016-08-02 12:32 ` Jiri Benc
  0 siblings, 0 replies; 2+ messages in thread
From: Jiri Benc @ 2016-08-02 12:32 UTC (permalink / raw)
  To: Baole Ni
  Cc: michal.simek, soren.brinkmann, bkenward, linux-driver,
	computersforpeace, m.chehab, pawel, m.szyprowski, kyungmin.park,
	k.kozlowski, netdev, linux-kernel, davem, jesse, linville,
	pshelar, daniel, hannes, tom, aduyck, chuansheng.liu

On Tue,  2 Aug 2016 19:42:14 +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/net/geneve.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/geneve.c b/drivers/net/geneve.c
> index cadefe4..2ddaa09 100644
> --- a/drivers/net/geneve.c
> +++ b/drivers/net/geneve.c
> @@ -32,7 +32,7 @@
>  #define VNI_HASH_SIZE		(1<<VNI_HASH_BITS)
>  
>  static bool log_ecn_error = true;
> -module_param(log_ecn_error, bool, 0644);
> +module_param(log_ecn_error, bool, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);

0644 is much more readable than the S_IGRL macros ("Incomprehensible
Group of Random Letters"). Most people use the octal value with chmod
and umask all the time while nobody is using the macros from the shell.
As a consequence, a quick glance at the number is enough to see what the
access rights are, while the macros need to be read carefully to
understand what's going on.

I very much dislike this patchset. It makes readability worse, not
better, and increases the likelihood of errors.

 Jiri

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-08-02 12:33 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-08-02 11:42 [PATCH 0746/1285] Replace numeric parameter like 0444 with macro Baole Ni
2016-08-02 12:32 ` Jiri Benc

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).