From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: firewire fixes for 6.4-rc4
Date: Thu, 1 Jun 2023 23:25:59 +0900 [thread overview]
Message-ID: <20230601142559.GA118570@workstation.local> (raw)
Hi Linus,
The following changes since commit 7877cb91f1081754a1487c144d85dc0d2e2e7fc4:
Linux 6.4-rc4 (2023-05-28 07:49:00 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git tags/firewire-fixes-6.4-rc4
for you to fetch changes up to 4420528254153189c70b6267593e445dc8654e37:
firewire: Replace zero-length array with flexible-array member (2023-06-01 22:41:14 +0900)
----------------------------------------------------------------
firewire fixes for 6.4-rc4
This pull request includes a single patch from the project for consecutive
effort of memory safety array. It brings no change to user space, thus it
is worth to apply it as a fix.
----------------------------------------------------------------
Gustavo A. R. Silva (1):
firewire: Replace zero-length array with flexible-array member
include/linux/firewire.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Regards
Takashi Sakamoto
reply other threads:[~2023-06-01 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230601142559.GA118570@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@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;
as well as URLs for NNTP newsgroup(s).