From: Christoph Hellwig <hch@infradead.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Kirti Wankhede <kwankhede@nvidia.com>,
Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] driver core: class: remove class_compat code
Date: Wed, 11 Dec 2024 20:27:59 -0800 [thread overview]
Message-ID: <Z1pmTxlEIEqeZf31@infradead.org> (raw)
In-Reply-To: <147a2a3e-8227-4f1b-9ab4-d0b4f261d2a6@gmail.com>
On Tue, Dec 03, 2024 at 09:08:55PM +0100, Heiner Kallweit wrote:
> vfio/mdev is the last user of class_compat, and it doesn't use it for
> the intended purpose. See kdoc of class_compat_register():
> Compatibility class are meant as a temporary user-space compatibility
> workaround when converting a family of class devices to a bus devices.
>
> In addition it uses only a part of the class_compat functionality.
> So inline the needed functionality, and afterwards all class_compat
> code can be removed.
Is there any reason it can't just be removed entirely?
prev parent reply other threads:[~2024-12-12 4:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 20:08 [PATCH 0/3] driver core: class: remove class_compat code Heiner Kallweit
2024-12-03 20:10 ` [PATCH 1/3] driver core: class: add class_pseudo_register Heiner Kallweit
2024-12-04 9:33 ` Greg Kroah-Hartman
2024-12-04 17:04 ` Heiner Kallweit
2024-12-04 18:17 ` Greg Kroah-Hartman
2024-12-04 19:35 ` Heiner Kallweit
2024-12-03 20:11 ` [PATCH 2/3] vfio/mdev: inline needed class_compat functionality Heiner Kallweit
2024-12-04 9:32 ` Greg Kroah-Hartman
2024-12-04 17:01 ` Heiner Kallweit
2024-12-04 18:16 ` Greg Kroah-Hartman
2024-12-04 19:30 ` Alex Williamson
2024-12-06 7:35 ` Heiner Kallweit
2024-12-06 7:42 ` Greg Kroah-Hartman
2024-12-06 16:37 ` Alex Williamson
2024-12-07 8:38 ` Greg Kroah-Hartman
2024-12-07 10:06 ` Heiner Kallweit
2024-12-07 10:23 ` Greg Kroah-Hartman
2024-12-12 4:42 ` Christoph Hellwig
2024-12-12 18:12 ` Alex Williamson
2024-12-12 18:21 ` Greg Kroah-Hartman
2024-12-12 18:39 ` Alex Williamson
2024-12-13 14:53 ` Christoph Hellwig
2024-12-06 17:05 ` Heiner Kallweit
2024-12-04 19:35 ` Heiner Kallweit
2025-01-10 14:35 ` Greg Kroah-Hartman
2025-01-13 22:09 ` Alex Williamson
2024-12-03 20:12 ` [PATCH 3/3] driver core: class: remove class_compat code Heiner Kallweit
2024-12-12 4:27 ` Christoph Hellwig [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=Z1pmTxlEIEqeZf31@infradead.org \
--to=hch@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=rafael@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 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.