From: Miroslav Benes <mbenes@suse.cz>
To: jpoimboe@redhat.com, sjenning@redhat.com, jkosina@suse.cz,
vojtech@suse.cz
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
pmladek@suse.cz, akpm@linux-foundation.org,
Miroslav Benes <mbenes@suse.cz>
Subject: [PATCH] livepatch: change ARCH_HAVE_LIVE_PATCHING to HAVE_LIVE_PATCHING
Date: Tue, 20 Jan 2015 12:49:35 +0100 [thread overview]
Message-ID: <1421754575-30071-1-git-send-email-mbenes@suse.cz> (raw)
Change ARCH_HAVE_LIVE_PATCHING to HAVE_LIVE_PATCHING in Kconfigs. HAVE_
bools are prevalent there and we should go with the flow.
Suggested-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Miroslav Benes <mbenes@suse.cz>
---
arch/x86/Kconfig | 2 +-
kernel/livepatch/Kconfig | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 460b31b..29b0952 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -17,7 +17,7 @@ config X86_64
depends on 64BIT
select X86_DEV_DMA_OPS
select ARCH_USE_CMPXCHG_LOCKREF
- select ARCH_HAVE_LIVE_PATCHING
+ select HAVE_LIVE_PATCHING
### Arch settings
config X86
diff --git a/kernel/livepatch/Kconfig b/kernel/livepatch/Kconfig
index 66797aa..347ee22 100644
--- a/kernel/livepatch/Kconfig
+++ b/kernel/livepatch/Kconfig
@@ -1,4 +1,4 @@
-config ARCH_HAVE_LIVE_PATCHING
+config HAVE_LIVE_PATCHING
bool
help
Arch supports kernel live patching
@@ -9,7 +9,7 @@ config LIVE_PATCHING
depends on MODULES
depends on SYSFS
depends on KALLSYMS_ALL
- depends on ARCH_HAVE_LIVE_PATCHING
+ depends on HAVE_LIVE_PATCHING
help
Say Y here if you want to support kernel live patching.
This option has no runtime impact until a kernel "patch"
--
2.1.2
next reply other threads:[~2015-01-20 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 11:49 Miroslav Benes [this message]
2015-01-20 12:49 ` Josh Poimboeuf
2015-01-20 16:09 ` Jiri Kosina
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=1421754575-30071-1-git-send-email-mbenes@suse.cz \
--to=mbenes@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=pmladek@suse.cz \
--cc=sjenning@redhat.com \
--cc=vojtech@suse.cz \
/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®