public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex@shazbot.org>
To: Jori Koolstra <jkoolstra@xs4all.nl>
Cc: gregkh@linuxfoundation.org, Kirti Wankhede <kwankhede@nvidia.com>,
	kvm@vger.kernel.org (open list:VFIO MEDIATED DEVICE DRIVERS),
	linux-kernel@vger.kernel.org (open list),
	alex@shazbot.org
Subject: Re: [PATCH v2] vfio: mdev: replace mtty_dev->vd_class with a const struct class
Date: Fri, 20 Mar 2026 15:17:54 -0600	[thread overview]
Message-ID: <20260320151754.3cefebec@shazbot.org> (raw)
In-Reply-To: <20260308214939.1215682-1-jkoolstra@xs4all.nl>

On Sun,  8 Mar 2026 22:49:39 +0100
Jori Koolstra <jkoolstra@xs4all.nl> wrote:

> The class_create() call has been deprecated in favor of class_register()
> as the driver core now allows for a struct class to be in read-only
> memory. Replace mtty_dev->vd_class with a const struct class and drop the
> class_create() call.
> 
> Compile tested and found no errors/warns in dmesg after enabling
> CONFIG_VFIO and CONFIG_SAMPLE_VFIO_MDEV_MTTY.
> 
> Link: https://lore.kernel.org/all/2023040244-duffel-pushpin-f738@gregkh/
> 
> Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Jori Koolstra <jkoolstra@xs4all.nl>
> ---
> v2: undo whitespace reformating of struct mtty_dev
> 
>  samples/vfio-mdev/mtty.c | 17 +++++++++--------
>  1 file changed, 9 insertions(+), 8 deletions(-)

Applied to vfio next branch for v7.1.  Thanks,

Alex

      parent reply	other threads:[~2026-03-20 21:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-08 21:49 [PATCH v2] vfio: mdev: replace mtty_dev->vd_class with a const struct class Jori Koolstra
2026-03-09  5:59 ` Greg KH
2026-03-20 21:17 ` 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=20260320151754.3cefebec@shazbot.org \
    --to=alex@shazbot.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkoolstra@xs4all.nl \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --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