All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Francesco Valla <francesco@valla.it>, qemu-devel@nongnu.org
Cc: Francesco Valla <francesco@valla.it>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] update-linux-headers: strip endianness-aware __counted_by
Date: Tue, 10 Nov 2026 11:30:51 +0100	[thread overview]
Message-ID: <87mrrhvuzo.fsf@redhat.com> (raw)
In-Reply-To: <20261107175443.29012-1-francesco@valla.it>

On Sat, Nov 07 2026, Francesco Valla <francesco@valla.it> wrote:

> Deal with the endianness-aware __counted_by_be() and __counted_by_le()
> annotations in Linux headers just like with __counted_by(): stripping
> them.
>
> Signed-off-by: Francesco Valla <francesco@valla.it>
> ---
>  scripts/update-linux-headers.sh | 2 ++
>  1 file changed, 2 insertions(+)

For virtio-can, I guess?

>
> diff --git a/scripts/update-linux-headers.sh b/scripts/update-linux-headers.sh
> index 3c3a0e9394d2..d3f843356507 100755
> --- a/scripts/update-linux-headers.sh
> +++ b/scripts/update-linux-headers.sh
> @@ -92,6 +92,8 @@ cp_portable() {
>          -e "$arch_cmd" \
>          -e 's/__bitwise//' \
>          -e 's/__counted_by(\w*)//' \
> +        -e 's/__counted_by_be(\w*)//' \
> +        -e 's/__counted_by_le(\w*)//' \
>          -e 's/__attribute__((packed))/QEMU_PACKED/' \
>          -e 's/__inline__/inline/' \
>          -e 's/__BITS_PER_LONG/HOST_LONG_BITS/' \

Not sure if we would want to kill all the __counted_by* birds with one
stone, but let's not overthink this.

Acked-by: Cornelia Huck <cohuck@redhat.com>



  reply	other threads:[~2026-11-10 10:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07 17:54 [PATCH] update-linux-headers: strip endianness-aware __counted_by Francesco Valla
2026-11-10 10:30 ` Cornelia Huck [this message]
2026-11-10 12:40   ` Francesco Valla

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=87mrrhvuzo.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=francesco@valla.it \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.