From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Baole Ni <baolex.ni@intel.com>
Cc: linux-s390@vger.kernel.org, k.kozlowski@samsung.com,
chuansheng.liu@intel.com, kvm@vger.kernel.org, pawel@osciak.com,
heiko.carstens@de.ibm.com, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
kyungmin.park@samsung.com, schwidefsky@de.ibm.com,
m.szyprowski@samsung.com, dwmw2@infradead.org,
m.chehab@samsung.com
Subject: Re: [PATCH 0904/1285] Replace numeric parameter like 0444 with macro
Date: Tue, 2 Aug 2016 16:11:44 +0200 [thread overview]
Message-ID: <20160802161144.538ee7a6.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20160802115646.10237-1-baolex.ni@intel.com>
On Tue, 2 Aug 2016 19:56:46 +0800
Baole Ni <baolex.ni@intel.com> 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/s390/virtio/virtio_ccw.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/s390/virtio/virtio_ccw.c b/drivers/s390/virtio/virtio_ccw.c
> index 8688ad4..56d3671 100644
> --- a/drivers/s390/virtio/virtio_ccw.c
> +++ b/drivers/s390/virtio/virtio_ccw.c
> @@ -1074,7 +1074,7 @@ static unsigned long devs_no_auto[__MAX_SSID + 1][__DEV_WORDS];
>
> static char *no_auto = "";
>
> -module_param(no_auto, charp, 0444);
> +module_param(no_auto, charp, S_IRUSR | S_IRGRP | S_IROTH);
> MODULE_PARM_DESC(no_auto, "list of ccw bus id ranges not to be auto-onlined");
>
> static int virtio_ccw_check_autoonline(struct ccw_device *cdev)
NACK. I find 0444 more readable.
<And some general remarks: Your patches are lacking a proper component
prefix and have a rather long list of people on to: ...and sending
1000+ patches to lkml at once is not a very good idea either.>
prev parent reply other threads:[~2016-08-02 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 11:56 [PATCH 0904/1285] Replace numeric parameter like 0444 with macro Baole Ni
2016-08-02 14:05 ` Christian Borntraeger
2016-08-02 14:11 ` Cornelia Huck [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=20160802161144.538ee7a6.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=baolex.ni@intel.com \
--cc=chuansheng.liu@intel.com \
--cc=dwmw2@infradead.org \
--cc=heiko.carstens@de.ibm.com \
--cc=k.kozlowski@samsung.com \
--cc=kvm@vger.kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=m.szyprowski@samsung.com \
--cc=pawel@osciak.com \
--cc=schwidefsky@de.ibm.com \
--cc=virtualization@lists.linux-foundation.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