From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967399AbcHBPdy (ORCPT ); Tue, 2 Aug 2016 11:33:54 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:40528 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934370AbcHBM0t (ORCPT ); Tue, 2 Aug 2016 08:26:49 -0400 Date: Tue, 2 Aug 2016 14:16:17 +0200 From: Greg KH To: Baole Ni Cc: cmetcalf@mellanox.com, dalias@libc.org, schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com, linux-kernel@vger.kernel.org, viresh.kumar@linaro.org, chuansheng.liu@intel.com Subject: Re: [PATCH 0029/1285] Replace numeric parameter like 0444 with macro Message-ID: <20160802121617.GA23006@kroah.com> References: <20160802103537.15705-1-baolex.ni@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160802103537.15705-1-baolex.ni@intel.com> User-Agent: Mutt/1.6.2 (2016-07-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 02, 2016 at 06:35:37PM +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. > > Signed-off-by: Chuansheng Liu > Signed-off-by: Baole Ni > --- > arch/tile/kernel/sysfs.c | 12 ++++++------ > 1 file changed, 6 insertions(+), 6 deletions(-) > > diff --git a/arch/tile/kernel/sysfs.c b/arch/tile/kernel/sysfs.c > index 825867c..cef3937 100644 > --- a/arch/tile/kernel/sysfs.c > +++ b/arch/tile/kernel/sysfs.c > @@ -38,7 +38,7 @@ static ssize_t chip_width_show(struct device *dev, > { > return sprintf(page, "%u\n", smp_width); > } > -static DEVICE_ATTR(chip_width, 0444, chip_width_show, NULL); > +static DEVICE_ATTR(chip_width, S_IRUSR | S_IRGRP | S_IROTH, chip_width_show, NULL); You do know about S_IRUGO, right? Why not use that? Same goes for your other replacements, use the correct #define, not a mix of values | together. And you are sending hundreds of patches with the same identical subject line, that's not ok, you need to make it unique for every patch. Usually that is done with the subsystem and driver name, see examples of this in the kernel changelogs. Please fix up and try again, in a much smaller series, before trying to do this across the whole kernel tree. good luck! greg k-h