From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH v3][next] tty: tty_buffer: Avoid hundreds of -Wflex-array-member-not-at-end warnings
Date: Thu, 6 Feb 2025 05:40:55 +0100 [thread overview]
Message-ID: <2025020633-irritate-boogieman-4c35@gregkh> (raw)
In-Reply-To: <Z6QvAZxiQusdaDkH@kspp>
On Thu, Feb 06, 2025 at 02:09:45PM +1030, Gustavo A. R. Silva wrote:
> diff --git a/include/linux/tty_buffer.h b/include/linux/tty_buffer.h
> index 31125e3be3c5..80a9d7832c97 100644
> --- a/include/linux/tty_buffer.h
> +++ b/include/linux/tty_buffer.h
> @@ -7,7 +7,7 @@
> #include <linux/mutex.h>
> #include <linux/workqueue.h>
>
> -struct tty_buffer {
> +struct tty_buffer_hdr {
> union {
> struct tty_buffer *next;
> struct llist_node free;
> @@ -15,9 +15,13 @@ struct tty_buffer {
> unsigned int used;
> unsigned int size;
> unsigned int commit;
> - unsigned int lookahead; /* Lazy update on recv, can become less than "read" */
> + unsigned int lookahead; /* Lazy update on recv, can become less than "read" */
Coding style change?
next prev parent reply other threads:[~2025-02-06 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 3:39 [PATCH v3][next] tty: tty_buffer: Avoid hundreds of -Wflex-array-member-not-at-end warnings Gustavo A. R. Silva
2025-02-06 4:40 ` Greg Kroah-Hartman [this message]
2025-02-06 23:23 ` Gustavo A. R. Silva
2025-02-07 9:38 ` Greg Kroah-Hartman
2025-02-06 9:12 ` Jiri Slaby
2025-02-06 9:23 ` Gustavo A. R. Silva
2025-02-11 7:02 ` 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=2025020633-irritate-boogieman-4c35@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=jirislaby@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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