From: Robin Voetter <robin@streamhpc.com>
To: Alex Williamson <alex.williamson@redhat.com>,
mst@redhat.com, marcel.apfelbaum@gmail.com
Cc: qemu-devel@nongnu.org, clg@redhat.com,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [RFC PATCH v2 2/4] vfio: Implement a common device info helper
Date: Wed, 31 May 2023 12:18:08 +0200 [thread overview]
Message-ID: <f64b3a82-a5b6-2f3f-74a1-062db2112224@streamhpc.com> (raw)
In-Reply-To: <20230526231558.1660396-3-alex.williamson@redhat.com>
On 5/27/23 01:15, Alex Williamson wrote:
> -static struct vfio_device_info *get_device_info(S390PCIBusDevice *pbdev,
> - uint32_t argsz)
> +static struct vfio_device_info *get_device_info(S390PCIBusDevice *pbdev);
> {
There is an extraneous semicolon here behind the function declaration
that should be removed.
Kind regards,
Robin Voetter, Stream HPC
next prev parent reply other threads:[~2023-05-31 10:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 23:15 [RFC PATCH v2 0/4] vfio/pci: Atomic Ops completer support Alex Williamson
2023-05-26 23:15 ` [RFC PATCH v2 1/4] linux-headers: Update for vfio capability reporting AtomicOps Alex Williamson
2023-05-30 13:19 ` Cédric Le Goater
2023-05-26 23:15 ` [RFC PATCH v2 2/4] vfio: Implement a common device info helper Alex Williamson
2023-05-31 10:18 ` Robin Voetter [this message]
2023-05-26 23:15 ` [RFC PATCH v2 3/4] pcie: Add a PCIe capability version helper Alex Williamson
2023-05-30 12:30 ` Cédric Le Goater
2023-05-31 22:02 ` Robin Voetter
2023-05-31 22:19 ` Philippe Mathieu-Daudé
2023-05-26 23:15 ` [RFC PATCH v2 4/4] vfio/pci: Enable AtomicOps completers on root ports Alex Williamson
2023-05-30 13:36 ` Cédric Le Goater
2023-05-31 22:03 ` Robin Voetter
2023-05-31 22:28 ` Philippe Mathieu-Daudé
2023-05-31 21:55 ` [RFC PATCH v2 0/4] vfio/pci: Atomic Ops completer support Robin Voetter
2023-05-31 22:24 ` Alex Williamson
2023-05-31 22:29 ` Philippe Mathieu-Daudé
2023-06-02 14:02 ` Philippe Mathieu-Daudé
2023-06-01 8:15 ` Robin Voetter
2023-05-31 22:31 ` 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=f64b3a82-a5b6-2f3f-74a1-062db2112224@streamhpc.com \
--to=robin@streamhpc.com \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=philmd@linaro.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).