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....@intel.com> Signed-off-by: Baole Ni <baolex...@intel.com> --- drivers/media/pci/bt8xx/bttv-input.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/media/pci/bt8xx/bttv-input.c b/drivers/media/pci/bt8xx/bttv-input.c index a75c53d..b422894 100644 --- a/drivers/media/pci/bt8xx/bttv-input.c +++ b/drivers/media/pci/bt8xx/bttv-input.c @@ -32,10 +32,10 @@ static int ir_debug; -module_param(ir_debug, int, 0644); +module_param(ir_debug, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH); static int ir_rc5_remote_gap = 885; -module_param(ir_rc5_remote_gap, int, 0644); +module_param(ir_rc5_remote_gap, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH); #undef dprintk #define dprintk(fmt, ...) \ -- 2.9.2 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
