From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
qemu-block@nongnu.org
Subject: [RFC PATCH 0/2] hw/usb/dev-uas: Fix Clang 11 -Wgnu-variable-sized-type-not-at-end error
Date: Mon, 18 Jan 2021 18:03:06 +0100 [thread overview]
Message-ID: <20210118170308.282442-1-philmd@redhat.com> (raw)
Another attempt to fix the following Clang 11 warning:
usb/dev-uas.c:157:31: error: field 'status' with variable sized type 'uas_i=
u' not at the end of a struct or class is a GNU extension [-Werror,-Wgnu-vari=
able-sized-type-not-at-end]
uas_iu status;
^
If a guest send a packet with additional data, respond
with "Illegal Request - parameter not supported".
Philippe Mathieu-Daud=C3=A9 (2):
scsi/utils: Add INVALID_PARAM_VALUE sense code definition
hw/usb/dev-uas: Report command additional adb length as unsupported
include/scsi/utils.h | 2 ++
hw/usb/dev-uas.c | 12 +++++++++++-
scsi/utils.c | 5 +++++
3 files changed, 18 insertions(+), 1 deletion(-)
--=20
2.26.2
next reply other threads:[~2021-01-18 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 17:03 Philippe Mathieu-Daudé [this message]
2021-01-18 17:03 ` [RFC PATCH 1/2] scsi/utils: Add INVALID_PARAM_VALUE sense code definition Philippe Mathieu-Daudé
2021-01-20 14:58 ` Eric Blake
2021-01-20 16:01 ` Gerd Hoffmann
2021-01-20 16:04 ` Philippe Mathieu-Daudé
2021-01-18 17:03 ` [RFC PATCH 2/2] hw/usb/dev-uas: Report command additional adb length as unsupported Philippe Mathieu-Daudé
2021-01-19 23:28 ` Philippe Mathieu-Daudé
2021-01-20 14:11 ` Eric Blake
2021-01-19 16:41 ` [RFC PATCH 0/2] hw/usb/dev-uas: Fix Clang 11 -Wgnu-variable-sized-type-not-at-end error Gerd Hoffmann
2021-01-19 16:49 ` Philippe Mathieu-Daudé
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=20210118170308.282442-1-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=fam@euphon.net \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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 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).