From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, gustavo@embeddedor.com
Subject: Re: [PATCH] Revert "firewire: Annotate struct fw_iso_packet with __counted_by()"
Date: Sat, 27 Jul 2024 10:36:57 +0900 [thread overview]
Message-ID: <20240727013657.GB163039@workstation.local> (raw)
In-Reply-To: <20240725161648.130404-1-o-takashi@sakamocchi.jp>
On Fri, Jul 26, 2024 at 01:16:48AM +0900, Takashi Sakamoto wrote:
> This reverts commit d3155742db89df3b3c96da383c400e6ff4d23c25.
>
> The header_length field is byte unit, thus it can not express the number of
> elements in header field.
>
> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> ---
> include/linux/firewire.h | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/firewire.h b/include/linux/firewire.h
> index 00abe0e5d602..1cca14cf5652 100644
> --- a/include/linux/firewire.h
> +++ b/include/linux/firewire.h
> @@ -462,9 +462,8 @@ struct fw_iso_packet {
> /* rx: Sync bit, wait for matching sy */
> u32 tag:2; /* tx: Tag in packet header */
> u32 sy:4; /* tx: Sy in packet header */
> - u32 header_length:8; /* Length of immediate header */
> - /* tx: Top of 1394 isoch. data_block */
> - u32 header[] __counted_by(header_length);
> + u32 header_length:8; /* Size of immediate header */
> + u32 header[]; /* tx: Top of 1394 isoch. data_block */
> };
>
> #define FW_ISO_CONTEXT_TRANSMIT 0
Applied to for-linus branch in firewire subsystem tree[1], with slight
change of comment. It would be sent to mainline today with another patch[2].
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git/log/?h=for-linus
[2] https://lore.kernel.org/stable/20240725155640.128442-1-o-takashi@sakamocchi.jp/
Regards
Takashi Sakamoto
prev parent reply other threads:[~2024-07-27 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 16:16 Takashi Sakamoto
2024-07-27 1:36 ` Takashi Sakamoto [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=20240727013657.GB163039@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=gustavo@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®