From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966795AbcHBNoF (ORCPT ); Tue, 2 Aug 2016 09:44:05 -0400 Received: from mga04.intel.com ([192.55.52.120]:29257 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966477AbcHBNn5 (ORCPT ); Tue, 2 Aug 2016 09:43:57 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,460,1464678000"; d="scan'208";a="858162159" From: Baole Ni To: perex@perex.cz, tiwai@suse.com, serge@hallyn.com, davem@davemloft.net, kadlec@blackhole.kfki.hu, m.szyprowski@samsung.com, kyungmin.park@samsung.com, k.kozlowski@samsung.com Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org, chuansheng.liu@intel.com, baolex.ni@intel.com, aryabinin@virtuozzo.com Subject: [PATCH 1191/1285] Replace numeric parameter like 0444 with macro Date: Tue, 2 Aug 2016 20:25:06 +0800 Message-Id: <20160802122506.29578-1-baolex.ni@intel.com> X-Mailer: git-send-email 2.9.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 Signed-off-by: Baole Ni --- sound/isa/sb/emu8000_patch.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/isa/sb/emu8000_patch.c b/sound/isa/sb/emu8000_patch.c index 71d13c0..0dd7c20 100644 --- a/sound/isa/sb/emu8000_patch.c +++ b/sound/isa/sb/emu8000_patch.c @@ -24,7 +24,7 @@ #include static int emu8000_reset_addr; -module_param(emu8000_reset_addr, int, 0444); +module_param(emu8000_reset_addr, int, S_IRUSR | S_IRGRP | S_IROTH); MODULE_PARM_DESC(emu8000_reset_addr, "reset write address at each time (makes slowdown)"); -- 2.9.2