From: Alex Williamson <alex.williamson@redhat.com>
To: kvm@vger.kernel.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
jgg@nvidia.com, clg@redhat.com, diana.craciun@oss.nxp.com
Subject: [PATCH 3/3] vfio/fsl: Create Kconfig sub-menu
Date: Fri, 2 Jun 2023 15:33:15 -0600 [thread overview]
Message-ID: <20230602213315.2521442-4-alex.williamson@redhat.com> (raw)
In-Reply-To: <20230602213315.2521442-1-alex.williamson@redhat.com>
For consistency with pci and platform, push the vfio-fsl-mc option into a
sub-menu.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
---
drivers/vfio/fsl-mc/Kconfig | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/vfio/fsl-mc/Kconfig b/drivers/vfio/fsl-mc/Kconfig
index 597d338c5c8a..d2757a1114aa 100644
--- a/drivers/vfio/fsl-mc/Kconfig
+++ b/drivers/vfio/fsl-mc/Kconfig
@@ -1,3 +1,5 @@
+menu "VFIO support for FSL_MC bus devices"
+
config VFIO_FSL_MC
tristate "VFIO support for QorIQ DPAA2 fsl-mc bus devices"
depends on FSL_MC_BUS
@@ -8,3 +10,5 @@ config VFIO_FSL_MC
fsl-mc bus devices using the VFIO framework.
If you don't know what to do here, say N.
+
+endmenu
--
2.39.2
next prev parent reply other threads:[~2023-06-02 21:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 21:33 [PATCH 0/3] vfio: Cleanup Kconfigs Alex Williamson
2023-06-02 21:33 ` [PATCH 1/3] vfio/pci: Cleanup Kconfig Alex Williamson
2023-06-05 9:21 ` Cédric Le Goater
2023-06-05 17:01 ` Jason Gunthorpe
2023-06-05 19:25 ` Alex Williamson
2023-06-06 14:25 ` Jason Gunthorpe
2023-06-06 21:57 ` Alex Williamson
2023-06-06 23:27 ` Jason Gunthorpe
2023-06-07 17:24 ` Alex Williamson
2023-06-07 13:33 ` Eric Auger
2023-06-02 21:33 ` [PATCH 2/3] vfio/platform: " Alex Williamson
2023-06-05 9:22 ` Cédric Le Goater
2023-06-07 13:32 ` Eric Auger
2023-06-07 19:04 ` Alex Williamson
2023-06-08 8:51 ` Eric Auger
2023-06-02 21:33 ` Alex Williamson [this message]
2023-06-05 9:22 ` [PATCH 3/3] vfio/fsl: Create Kconfig sub-menu Cédric Le Goater
2023-06-07 13:34 ` Eric Auger
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=20230602213315.2521442-4-alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=diana.craciun@oss.nxp.com \
--cc=jgg@nvidia.com \
--cc=kvm@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 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.