From: Alex Williamson <alex.williamson@redhat.com>
To: "Ricardo B. Marliere" <ricardo@marliere.net>
Cc: Kirti Wankhede <kwankhede@nvidia.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 0/2] vfio: constify struct class usage
Date: Tue, 5 Mar 2024 16:12:32 -0700 [thread overview]
Message-ID: <20240305161232.1cf094c0.alex.williamson@redhat.com> (raw)
In-Reply-To: <20240301-class_cleanup-vfio-v1-0-9236d69083f5@marliere.net>
On Fri, 01 Mar 2024 14:51:46 -0300
"Ricardo B. Marliere" <ricardo@marliere.net> wrote:
> This is a simple and straight forward cleanup series that aims to make the
> class structures in vfio constant. This has been possible since 2023 [1].
>
> ---
> [1]: https://lore.kernel.org/all/2023040248-customary-release-4aec@gregkh/
>
> To: Kirti Wankhede <kwankhede@nvidia.com>
> Cc: kvm@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Ricardo B. Marliere <ricardo@marliere.net>
>
> ---
> Ricardo B. Marliere (2):
> vfio/mdpy: make mdpy_class constant
> vfio/mbochs: make mbochs_class constant
>
> samples/vfio-mdev/mbochs.c | 18 ++++++++----------
> samples/vfio-mdev/mdpy.c | 18 ++++++++----------
> 2 files changed, 16 insertions(+), 20 deletions(-)
> ---
> base-commit: 87adedeba51a822533649b143232418b9e26d08b
> change-id: 20240301-class_cleanup-vfio-3c5f72230ba5
>
> Best regards,
Applied to vfio next branch for v6.9. Thanks,
Alex
prev parent reply other threads:[~2024-03-05 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 17:51 [PATCH 0/2] vfio: constify struct class usage Ricardo B. Marliere
2024-03-01 17:51 ` [PATCH 1/2] vfio/mdpy: make mdpy_class constant Ricardo B. Marliere
2024-03-01 17:51 ` [PATCH 2/2] vfio/mbochs: make mbochs_class constant Ricardo B. Marliere
2024-03-05 23:12 ` 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=20240305161232.1cf094c0.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ricardo@marliere.net \
/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