From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Baole Ni <baolex.ni@intel.com>
Cc: dvhart@infradead.org, ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, chuansheng.liu@intel.com
Subject: Re: [PATCH 0857/1285] Replace numeric parameter like 0444 with macro
Date: Tue, 2 Aug 2016 14:34:07 -0300 [thread overview]
Message-ID: <20160802173407.GA1939@khazad-dum.debian.net> (raw)
In-Reply-To: <20160802115249.7120-1-baolex.ni@intel.com>
(cc list trimmed)
On Tue, 02 Aug 2016, 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 <chuansheng.liu@intel.com>
> Signed-off-by: Baole Ni <baolex.ni@intel.com>
NACK.
IMO, the proposed change reduces readiability for no good reason. Most
people touching kernel code have 0444, 0644, 0755, etc. already
hardwired into their pattern recognition neural network, while the POSIX
S_* crap is actually bug food.
PS: no more ill-managed ultra-large patch bombs, *please*.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2016-08-02 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 11:52 [PATCH 0857/1285] Replace numeric parameter like 0444 with macro Baole Ni
2016-08-02 17:34 ` Henrique de Moraes Holschuh [this message]
2016-08-05 22:57 ` Darren Hart
2016-08-08 6:41 ` Ni, BaoleX
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160802173407.GA1939@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=baolex.ni@intel.com \
--cc=chuansheng.liu@intel.com \
--cc=dvhart@infradead.org \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox