mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: alex.williamson@redhat.com, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, eric.auger@redhat.com,
	smostafa@google.com, praan@google.com
Subject: [PATCH 0/2] vfio/platform: Deprecate vfio-amba and reset drivers
Date: Mon, 25 Aug 2025 11:57:59 -0600	[thread overview]
Message-ID: <20250825175807.3264083-1-alex.williamson@redhat.com> (raw)

Based on discussion[1] there's still interest in keeping vfio-platform
itself, but the use case doesn't involve any of the current reset
drivers and doesn't include vfio-amba.  To give any users a chance to
speak up, let's mark these as deprecated and generate logs if they're
used.

I intend to pull the vfio/fsl-mc removal from the previous series given
there were no objections.  Thanks,

Alex

[1] https://lore.kernel.org/all/20250806170314.3768750-1-alex.williamson@redhat.com/

Alex Williamson (2):
  vfio/amba: Mark for removal
  vfio/platform: Mark reset drivers for removal

 drivers/vfio/platform/Kconfig                            | 5 ++++-
 drivers/vfio/platform/reset/Kconfig                      | 6 +++---
 drivers/vfio/platform/reset/vfio_platform_amdxgbe.c      | 2 ++
 drivers/vfio/platform/reset/vfio_platform_bcmflexrm.c    | 2 ++
 drivers/vfio/platform/reset/vfio_platform_calxedaxgmac.c | 2 ++
 drivers/vfio/platform/vfio_amba.c                        | 2 ++
 6 files changed, 15 insertions(+), 4 deletions(-)

-- 
2.50.1


             reply	other threads:[~2025-08-25 17:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 17:57 Alex Williamson [this message]
2025-08-25 17:58 ` [PATCH 1/2] vfio/amba: Mark for removal Alex Williamson
2025-08-25 17:58 ` [PATCH 2/2] vfio/platform: Mark reset drivers " Alex Williamson
2025-08-26  5:56 ` [PATCH 0/2] vfio/platform: Deprecate vfio-amba and reset drivers Eric Auger
2025-09-01 21:31 ` Mostafa Saleh
2025-09-01 22:05 ` Pranjal Shrivastava

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=20250825175807.3264083-1-alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=praan@google.com \
    --cc=smostafa@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®