All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: cgel.zte@gmail.com
Cc: gor@linux.ibm.com, agordeev@linux.ibm.com,
	borntraeger@linux.ibm.com, svens@linux.ibm.com,
	lv.ruyi@zte.com.cn, egorenar@linux.ibm.com,
	oberpar@linux.ibm.com, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org, Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH] s390: replace zero-length array with flexible-array member
Date: Mon, 4 Apr 2022 11:14:36 +0200	[thread overview]
Message-ID: <Ykq2/JEubkdX7GWR@osiris> (raw)
In-Reply-To: <20220401075639.2407457-1-lv.ruyi@zte.com.cn>

On Fri, Apr 01, 2022 at 07:56:39AM +0000, cgel.zte@gmail.com wrote:
> From: Lv Ruyi <lv.ruyi@zte.com.cn>
> 
> There is a regular need in the kernel to provide a way to declare
> having a dynamically sized set of trailing elements in a structure.
> Kernel code should always use “flexible array members”[1] for these
> cases. The older style of one-element or zero-length arrays should
> no longer be used[2].
> 
> [1] https://en.wikipedia.org/wiki/Flexible_array_member
> [2] https://www.kernel.org/doc/html/v5.16/process/deprecated.html#zero-length-and-one-element-arrays
> 
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Lv Ruyi <lv.ruyi@zte.com.cn>
> ---
>  drivers/s390/char/sclp_cmd.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Please resend with a proper sign-off chain. Thanks!

  reply	other threads:[~2022-04-04  9:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  7:56 [PATCH] s390: replace zero-length array with flexible-array member cgel.zte
2022-04-04  9:14 ` Heiko Carstens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-21 15:06 [PATCH] s390: Replace " Gustavo A. R. Silva
2020-02-25 13:57 ` Vasily Gorbik
2020-02-25 14:05   ` Gustavo A. R. Silva

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=Ykq2/JEubkdX7GWR@osiris \
    --to=hca@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=cgel.zte@gmail.com \
    --cc=egorenar@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=lv.ruyi@zte.com.cn \
    --cc=oberpar@linux.ibm.com \
    --cc=svens@linux.ibm.com \
    --cc=zealci@zte.com.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.