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 <redacted>
Signed-off-by: Baole Ni <redacted>
---
drivers/edac/pasemi_edac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Olof Johansson <hidden> Date: 2016-08-02 19:00:51
On Tue, Aug 02, 2016 at 06:45:15PM +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.
Am I the only one who find the readability to be MUCH better for the
numeric values?
-Olof
On Tue, Aug 02, 2016 at 11:54:47AM -0700, Olof Johansson wrote:
On Tue, Aug 02, 2016 at 06:45:15PM +0800, Baole Ni wrote:
quoted
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.
Am I the only one who find the readability to be MUCH better for the
numeric values?
You are not the only one. Robustness is a non-issue here as well (except
that this patch series showed that some mail servers struggle to handle
1285 emails).
Segher