Linux Hardening
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Clemens Ladisch <clemens@ladisch.de>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Kees Cook <keescook@chromium.org>,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
	alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/2][next] firewire: Avoid -Wflex-array-member-not-at-end warnings
Date: Wed, 6 Mar 2024 10:18:59 -0600	[thread overview]
Message-ID: <6a7854af-a183-4db2-8400-4d9eb0cc4308@embeddedor.com> (raw)
In-Reply-To: <20240306011030.GA71684@workstation.local>


> Thanks for the improvements, however we are mostly at the end of
> development period for v6.8 kernel. Let me postpone applying the patches
> until closing the next merge window (for v6.9), since we need the term to
> evaluate the change. I mean that it goes to v6.10 kernel.

Sure, no problem.

Actually, I'll send a v2 with DEFINE_FLEX(), instead.

Thanks
--
Gustavo

  reply	other threads:[~2024-03-06 16:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 17:24 [PATCH 0/2][next] firewire: Avoid -Wflex-array-member-not-at-end warnings Gustavo A. R. Silva
2024-03-05 17:24 ` [PATCH 1/2][next] firewire: Avoid -Wflex-array-member-not-at-end warning Gustavo A. R. Silva
2024-03-05 17:25 ` [PATCH 2/2][next] ALSA: firewire-lib: " Gustavo A. R. Silva
2024-03-06  1:10 ` [PATCH 0/2][next] firewire: Avoid -Wflex-array-member-not-at-end warnings Takashi Sakamoto
2024-03-06 16:18   ` Gustavo A. R. Silva [this message]
2024-04-29 18:30     ` Kees Cook
2024-04-29 18:42       ` Gustavo A. R. Silva
2024-04-29 19:50         ` Kees Cook

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=6a7854af-a183-4db2-8400-4d9eb0cc4308@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=gustavoars@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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