All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Roque Arcudia Hernandez <roqueh@google.com>,
	richard.henderson@linaro.org, jansene@google.com, mjt@tls.msk.ru
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
	QEMU Trivial <qemu-trivial@nongnu.org>
Subject: Re: [PATCH] hw/usb: Use __attribute__((packed)) vs __packed
Date: Mon, 4 Nov 2024 08:37:46 +0100	[thread overview]
Message-ID: <6f67908f-7ca7-4aa2-86e2-99b79aa6b4e7@redhat.com> (raw)
In-Reply-To: <20241101211720.3354111-1-roqueh@google.com>

On 01/11/2024 22.17, Roque Arcudia Hernandez wrote:
> __packed is non standard and is not present in clang-cl.
> __attribute__((packed)) has the same semantics.
> 
> Signed-off-by: Erwin Jansen <jansene@google.com>
> Signed-off-by: Roque Arcudia Hernandez <roqueh@google.com>
> ---
>   include/hw/usb/dwc2-regs.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/hw/usb/dwc2-regs.h b/include/hw/usb/dwc2-regs.h
> index 523b112c5e..b8b4266543 100644
> --- a/include/hw/usb/dwc2-regs.h
> +++ b/include/hw/usb/dwc2-regs.h
> @@ -838,7 +838,7 @@
>   struct dwc2_dma_desc {
>           uint32_t status;
>           uint32_t buf;
> -} __packed;
> +} QEMU_PACKED;

Reviewed-by: Thomas Huth <thuth@redhat.com>

Actually, the struct only consists of two 32-bit values, so I doubt that the 
"packed" is needed here at all. Maybe we could even simply remove it?

  Thomas



  parent reply	other threads:[~2024-11-04  7:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 21:17 [PATCH] hw/usb: Use __attribute__((packed)) vs __packed Roque Arcudia Hernandez
2024-11-01 21:32 ` Pierrick Bouvier
2024-11-04  7:37 ` Thomas Huth [this message]
2024-11-21 10:01   ` Michael Tokarev
2024-11-21 10:24     ` Thomas Huth
2024-11-21 11:23       ` Paolo Bonzini

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=6f67908f-7ca7-4aa2-86e2-99b79aa6b4e7@redhat.com \
    --to=thuth@redhat.com \
    --cc=jansene@google.com \
    --cc=kraxel@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=roqueh@google.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 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.