From: Alex Williamson <alex.williamson@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: kvm@vger.kernel.org, Cornelia Huck <cohuck@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] include/uapi/linux/vfio.h: Fix trivial typo - _IORW should be _IOWR instead
Date: Wed, 18 May 2022 11:51:19 -0600 [thread overview]
Message-ID: <20220518115119.2e618c39.alex.williamson@redhat.com> (raw)
In-Reply-To: <20220516101202.88373-1-thuth@redhat.com>
On Mon, 16 May 2022 12:12:02 +0200
Thomas Huth <thuth@redhat.com> wrote:
> There is no macro called _IORW, so use _IOWR in the comment instead.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> include/uapi/linux/vfio.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
> index fea86061b44e..733a1cddde30 100644
> --- a/include/uapi/linux/vfio.h
> +++ b/include/uapi/linux/vfio.h
> @@ -643,7 +643,7 @@ enum {
> };
>
> /**
> - * VFIO_DEVICE_GET_PCI_HOT_RESET_INFO - _IORW(VFIO_TYPE, VFIO_BASE + 12,
> + * VFIO_DEVICE_GET_PCI_HOT_RESET_INFO - _IOWR(VFIO_TYPE, VFIO_BASE + 12,
> * struct vfio_pci_hot_reset_info)
> *
> * Return: 0 on success, -errno on failure:
> @@ -770,7 +770,7 @@ struct vfio_device_ioeventfd {
> #define VFIO_DEVICE_IOEVENTFD _IO(VFIO_TYPE, VFIO_BASE + 16)
>
> /**
> - * VFIO_DEVICE_FEATURE - _IORW(VFIO_TYPE, VFIO_BASE + 17,
> + * VFIO_DEVICE_FEATURE - _IOWR(VFIO_TYPE, VFIO_BASE + 17,
> * struct vfio_device_feature)
> *
> * Get, set, or probe feature data of the device. The feature is selected
Applied to vfio next branch for v5.19. Thanks!
Alex
prev parent reply other threads:[~2022-05-18 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 10:12 Thomas Huth
2022-05-16 10:27 ` Cornelia Huck
2022-05-18 17:51 ` Alex Williamson [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=20220518115119.2e618c39.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thuth@redhat.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 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®