From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Cc: "Thomas Weißschuh" <linux@weissschuh.net>, linux-kernel@vger.kernel.org
Subject: [PATCH] xen/privcmd: make option visible in Kconfig
Date: Sat, 13 Nov 2021 09:38:21 +0100 [thread overview]
Message-ID: <20211113083821.71060-1-linux@weissschuh.net> (raw)
This configuration option provides a misc device as an API to userspace.
Make this API usable without having to select the module as a transitive
dependency.
This also fixes an issue where localyesconfig would select
CONFIG_XEN_PRIVCMD=m because it was not visible and defaulted to
building as module.
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
---
Note: If CONFIG_XEN_PRIVCMD really is only meant to be selected by
XENFS, then the issue can be fixed by removing its "default m"
definition.
---
drivers/xen/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig
index a1b11c62da9e..c14d8631b8f6 100644
--- a/drivers/xen/Kconfig
+++ b/drivers/xen/Kconfig
@@ -259,7 +259,7 @@ config XEN_SCSI_BACKEND
if guests need generic access to SCSI devices.
config XEN_PRIVCMD
- tristate
+ tristate "Xen privileged domain-0 commands"
depends on XEN
default m
base-commit: 66f4beaa6c1d28161f534471484b2daa2de1dce0
--
2.33.1
next reply other threads:[~2021-11-13 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 8:38 Thomas Weißschuh [this message]
2021-11-15 10:02 ` Jan Beulich
2021-11-15 10:25 ` Thomas Weißschuh
2021-11-16 14:33 Juergen Gross
2021-11-16 14:55 ` Jan Beulich
2021-11-16 15:01 ` Juergen Gross
2021-11-16 16:05 ` Jan Beulich
2021-11-16 22:33 ` Boris Ostrovsky
2021-11-17 16:05 ` Boris Ostrovsky
2021-11-16 14:59 ` Thomas Weißschuh
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=20211113083821.71060-1-linux@weissschuh.net \
--to=linux@weissschuh.net \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®