From: Jonathan Corbet <corbet@lwn.net>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>
Subject: Re: [PATCH v3] docs: deprecated.rst: Add zero-length and one-element arrays
Date: Fri, 19 Jun 2020 13:39:27 -0600 [thread overview]
Message-ID: <20200619133927.654ab7d2@lwn.net> (raw)
In-Reply-To: <20200608213711.GA22271@embeddedor>
On Mon, 8 Jun 2020 16:37:11 -0500
"Gustavo A. R. Silva" <gustavoars@kernel.org> wrote:
> Add zero-length and one-element arrays to the list.
>
> While I continue replacing zero-length and one-element arrays with
> flexible-array members, I need a reference to point people to, so
> they don't introduce more instances of such arrays. And while here,
> add a note to the "open-coded arithmetic in allocator arguments"
> section, on the use of struct_size() and the arrays-to-deprecate
> mentioned here.
>
> Co-developed-by: Kees Cook <keescook@chromium.org>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
> ---
> Changes in v3:
> - Add changes written by Kees.
> - Add Co-developed-by tag to include Kees in the changelog text.
>
> Changes in v2:
> - Adjust some markup links for readability.
>
> Documentation/process/deprecated.rst | 118 +++++++++++++++++++++++++++
> 1 file changed, 118 insertions(+)
Applied, thanks.
jon
prev parent reply other threads:[~2020-06-19 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 21:37 [PATCH v3] docs: deprecated.rst: Add zero-length and one-element arrays Gustavo A. R. Silva
2020-06-10 5:56 ` Kees Cook
2020-06-19 19:39 ` Jonathan Corbet [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=20200619133927.654ab7d2@lwn.net \
--to=corbet@lwn.net \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).