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 <[email protected]>
Signed-off-by: Baole Ni <[email protected]>
---
 kernel/time/sched_clock.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/time/sched_clock.c b/kernel/time/sched_clock.c
index a26036d..9d072c3 100644
--- a/kernel/time/sched_clock.c
+++ b/kernel/time/sched_clock.c
@@ -71,7 +71,7 @@ struct clock_data {
 static struct hrtimer sched_clock_timer;
 static int irqtime = -1;
 
-core_param(irqtime, irqtime, int, 0400);
+core_param(irqtime, irqtime, int, S_IRUSR);
 
 static u64 notrace jiffy_sched_clock_read(void)
 {
-- 
2.9.2

Reply via email to