From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Ian Jackson <iwj@xenproject.org>, Julien Grall <julien@xen.org>,
Wei Liu <wl@xen.org>, Stefano Stabellini <sstabellini@kernel.org>
Subject: [PATCH] common/Kconfig: sort HAS_*
Date: Tue, 22 Sep 2020 09:47:19 +0200 [thread overview]
Message-ID: <5b40fddf-3d43-a105-2528-a448b2df020a@suse.com> (raw)
Later additions look to have been put at the end, with MEM_ACCESS*
somewhere in the middle. Re-sort this part of the file, in the hope that
future additions will be made noticing the intentions here.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
--- a/xen/common/Kconfig
+++ b/xen/common/Kconfig
@@ -34,16 +34,11 @@ config HAS_EX_TABLE
config HAS_FAST_MULTIPLY
bool
-config MEM_ACCESS_ALWAYS_ON
+config HAS_IOPORTS
bool
-config MEM_ACCESS
- def_bool MEM_ACCESS_ALWAYS_ON
- prompt "Memory Access and VM events" if !MEM_ACCESS_ALWAYS_ON
- ---help---
-
- Framework to configure memory access types for guests and receive
- related events in userspace.
+config HAS_KEXEC
+ bool
config HAS_MEM_PAGING
bool
@@ -51,17 +46,22 @@ config HAS_MEM_PAGING
config HAS_PDX
bool
-config HAS_UBSAN
+config HAS_SCHED_GRANULARITY
bool
-config HAS_KEXEC
+config HAS_UBSAN
bool
-config HAS_IOPORTS
+config MEM_ACCESS_ALWAYS_ON
bool
-config HAS_SCHED_GRANULARITY
- bool
+config MEM_ACCESS
+ def_bool MEM_ACCESS_ALWAYS_ON
+ prompt "Memory Access and VM events" if !MEM_ACCESS_ALWAYS_ON
+ ---help---
+
+ Framework to configure memory access types for guests and receive
+ related events in userspace.
config NEEDS_LIBELF
bool
next reply other threads:[~2020-09-22 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 7:47 Jan Beulich [this message]
2020-09-22 9:09 ` [PATCH] common/Kconfig: sort HAS_* Julien Grall
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=5b40fddf-3d43-a105-2528-a448b2df020a@suse.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=iwj@xenproject.org \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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 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.