From: Stefan Hajnoczi <stefanha@redhat.com>
To: David Laight <David.Laight@aculab.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Tian, Kevin" <kevin.tian@intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH v2 0/3] vfio: use __aligned_u64 for ioctl structs
Date: Wed, 30 Aug 2023 17:53:57 -0400 [thread overview]
Message-ID: <20230830215357.GB480691@fedora> (raw)
In-Reply-To: <3e8b6e0503a84c93b6dd44c0d311abfe@AcuMS.aculab.com>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
On Tue, Aug 29, 2023 at 09:10:06PM +0000, David Laight wrote:
> From: Stefan Hajnoczi
> > Sent: 29 August 2023 19:27
> >
> > v2:
> > - Rebased onto https://github.com/awilliam/linux-vfio.git next to get the
> > vfio_iommu_type1_info pad field [Kevin]
> > - Fixed min(minsz, sizeof(dmabuf)) -> min(dmabuf.argsz, sizeof(dmabuf)) [Jason, Kevin]
>
> You managed to use min_t() instead of fixing the types to match.
I'm not sure what you're referring to here. Can you explain which line
of code and what you'd like to see changed?
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-08-30 21:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 18:27 [PATCH v2 0/3] vfio: use __aligned_u64 for ioctl structs Stefan Hajnoczi
2023-08-29 18:27 ` [PATCH v2 1/3] vfio: trivially " Stefan Hajnoczi
2023-08-31 8:45 ` Philippe Mathieu-Daudé
2023-09-11 6:06 ` Tian, Kevin
2023-08-29 18:27 ` [PATCH v2 2/3] vfio: use __aligned_u64 in struct vfio_device_gfx_plane_info Stefan Hajnoczi
2023-09-07 16:25 ` Jason Gunthorpe
2023-09-11 6:07 ` Tian, Kevin
2023-09-15 20:04 ` Alex Williamson
2023-09-18 14:15 ` Stefan Hajnoczi
2023-08-29 18:27 ` [PATCH v2 3/3] vfio: use __aligned_u64 in struct vfio_device_ioeventfd Stefan Hajnoczi
2023-09-11 6:08 ` Tian, Kevin
2023-08-29 21:10 ` [PATCH v2 0/3] vfio: use __aligned_u64 for ioctl structs David Laight
2023-08-30 8:32 ` David Laight
2023-08-30 21:53 ` Stefan Hajnoczi [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=20230830215357.GB480691@fedora \
--to=stefanha@redhat.com \
--cc=David.Laight@aculab.com \
--cc=alex.williamson@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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