From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, tiwai@suse.de,
edmund.raile@proton.me
Subject: [GIT PULL] firewire fixes for v6.11-rc1
Date: Sat, 27 Jul 2024 10:51:47 +0900 [thread overview]
Message-ID: <20240727015147.GA163457@workstation.local> (raw)
Hi Linus,
Please apply the following changes for v6.11 kernel to fix some
regressions appended to v6.10 kernel. They include the change of sound
subsystem and I have got an ack of sound subsystem maintainer.
The following changes since commit 06dcc4c9baa9e92896f00d02ffa760c0988b4371:
firewire: core: move copy_port_status() helper function to TP_fast_assign() block (2024-07-12 14:34:12 +0900)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git tags/firewire-fixes-6.11-rc1
for you to fetch changes up to c1839501fe3e67d98635f159dba8b170d08f6521:
ALSA: firewire-lib: fix wrong value as length of header for CIP_NO_HEADER case (2024-07-27 10:28:36 +0900)
----------------------------------------------------------------
firewire fixes for 6.11-rc1
Two commits are included to fix some regressions. These commits should also
be applied to the v6.10 kernel as well.
The recent integration of compiler collections introduced the technology
to check flexible array length at runtime by providing proper annotations.
In v6.10 kernel, a patch was merged into firewire subsystem to utilize it,
however the annotation was inadequate. There is also the related change for
the flexible array in sound subsystem, but it causes a regression where
the data in the payload of isochronous packet is incorrect for some
devices. These bugs are now fixed.
----------------------------------------------------------------
Takashi Sakamoto (2):
Revert "firewire: Annotate struct fw_iso_packet with __counted_by()"
ALSA: firewire-lib: fix wrong value as length of header for CIP_NO_HEADER case
include/linux/firewire.h | 5 ++---
sound/firewire/amdtp-stream.c | 3 +--
2 files changed, 3 insertions(+), 5 deletions(-)
Thanks
Takashi Sakamoto
next reply other threads:[~2024-07-27 1:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 1:51 Takashi Sakamoto [this message]
2024-07-27 20:07 ` [GIT PULL] firewire fixes for v6.11-rc1 pr-tracker-bot
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=20240727015147.GA163457@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=edmund.raile@proton.me \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
--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