Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1455253
| From | Baole Ni <baolex.ni@intel.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [PATCH 0242/1285] Replace numeric parameter like 0444 with macro |
| Date | 2016-08-02 20:10 +0200 |
| Message-ID | <s1MiD-84F-79@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
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/hwtracing/stm/dummy_stm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/hwtracing/stm/dummy_stm.c b/drivers/hwtracing/stm/dummy_stm.c index a86612d..7c82ae2 100644 --- a/drivers/hwtracing/stm/dummy_stm.c +++ b/drivers/hwtracing/stm/dummy_stm.c @@ -46,11 +46,11 @@ static struct stm_data dummy_stm[DUMMY_STM_MAX]; static int nr_dummies = 4; -module_param(nr_dummies, int, 0400); +module_param(nr_dummies, int, S_IRUSR); static unsigned int fail_mode; -module_param(fail_mode, int, 0600); +module_param(fail_mode, int, S_IRUSR | S_IWUSR); static int dummy_stm_link(struct stm_data *data, unsigned int master, unsigned int channel) -- 2.9.2
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
[PATCH 0242/1285] Replace numeric parameter like 0444 with macro Baole Ni <baolex.ni@intel.com> - 2016-08-02 20:10 +0200
csiph-web