From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Baole Ni <baolex.ni@intel.com>
Cc: airlied@linux.ie, kyungmin.park@samsung.com, kgene@kernel.org,
k.kozlowski@samsung.com, dougthompson@xmission.com, bp@alien8.de,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
airlied@redhat.com, daniel.vetter@ffwll.ch, treding@nvidia.com,
alexander.deucher@amd.com, ville.syrjala@linux.intel.com,
chuansheng.liu@intel.com
Subject: Re: [PATCH 0210/1285] Replace numeric parameter like 0444 with macro
Date: Wed, 3 Aug 2016 17:23:32 +0200 [thread overview]
Message-ID: <20160803152332.GA8124@kozik-book> (raw)
In-Reply-To: <20160802105001.27759-1-baolex.ni@intel.com>
On Tue, Aug 02, 2016 at 06:50:01PM +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 <chuansheng.liu@intel.com>
> Signed-off-by: Baole Ni <baolex.ni@intel.com>
> ---
> drivers/gpu/drm/qxl/qxl_drv.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
I got almost 1000 patches out of your mail bomb. For all of them: NACK.
Other people pointed actual reasons (title, readability, cc-list). The
commit msg should be also written in a more readable way.
Anyway, in Intel there are a lot of people having kernel contributions
so it is a shame that you didn't ask them for advice how to do it...
BR,
Krzysztof
prev parent reply other threads:[~2016-08-03 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 10:50 [PATCH 0210/1285] Replace numeric parameter like 0444 with macro Baole Ni
2016-08-03 15:23 ` Krzysztof Kozlowski [this message]
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=20160803152332.GA8124@kozik-book \
--to=k.kozlowski@samsung.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=baolex.ni@intel.com \
--cc=bp@alien8.de \
--cc=chuansheng.liu@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dougthompson@xmission.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=treding@nvidia.com \
--cc=ville.syrjala@linux.intel.com \
/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