From: Vasily Gorbik <gor@linux.ibm.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: Eric Farman <farman@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Tony Krowiak <akrowiak@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Holger Dengler <dengler@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Thorsten Blum <thorsten.blum@linux.dev>
Subject: Re: [PATCH 0/2] s390/vfio-*: make mdev_types unlike a fake flex array
Date: Tue, 18 Feb 2025 17:38:06 +0100 [thread overview]
Message-ID: <your-ad-here.call-01739896686-ext-9687@work.hours> (raw)
In-Reply-To: <20250217100614.3043620-1-pasic@linux.ibm.com>
On Mon, Feb 17, 2025 at 11:06:12AM +0100, Halil Pasic wrote:
>
> One sized trailing array members can look like fake flex arrays and
> confuse people. Let us try to make the mdev_types member of the parent
> devices in vfio-ap and vfio-ccw less confusing.
>
>
> Halil Pasic (2):
> s390/vfio-ap: make mdev_types not look like a fake flex array
> s390/vfio-ccw: make mdev_types not look like a fake flex array
>
> drivers/s390/cio/vfio_ccw_drv.c | 6 +++---
> drivers/s390/cio/vfio_ccw_private.h | 2 +-
> drivers/s390/crypto/vfio_ap_ops.c | 4 ++--
> drivers/s390/crypto/vfio_ap_private.h | 2 +-
> 4 files changed, 7 insertions(+), 7 deletions(-)
Applied, thank you!
prev parent reply other threads:[~2025-02-18 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 10:06 [PATCH 0/2] s390/vfio-*: make mdev_types unlike a fake flex array Halil Pasic
2025-02-17 10:06 ` [PATCH 1/2] s390/vfio-ap: make mdev_types not look like " Halil Pasic
2025-02-17 10:06 ` [PATCH 2/2] s390/vfio-ccw: " Halil Pasic
2025-02-18 16:38 ` Vasily Gorbik [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=your-ad-here.call-01739896686-ext-9687@work.hours \
--to=gor@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=dengler@linux.ibm.com \
--cc=farman@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gustavo@embeddedor.com \
--cc=hca@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=thorsten.blum@linux.dev \
--cc=vneethv@linux.ibm.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.