From: john.garry@huawei.com (John Garry)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drivers/perf: Remove ARM_SPE_PMU explicit PERF_EVENTS dependency
Date: Tue, 22 May 2018 23:54:04 +0800 [thread overview]
Message-ID: <1527004444-239462-1-git-send-email-john.garry@huawei.com> (raw)
Since commit bddb9b68d3fb ("drivers/perf: commonise PERF_EVENTS
dependency"), all perf drivers depend on PERF_EVENTS config under a
common menu.
Config ARM_SPE_PMU still declares explicitly a dependency on
PERF_EVENTS, which is unneeded, so remove it.
Signed-off-by: John Garry <john.garry@huawei.com>
diff --git a/drivers/perf/Kconfig b/drivers/perf/Kconfig
index 28bb5a0..90ce4da 100644
--- a/drivers/perf/Kconfig
+++ b/drivers/perf/Kconfig
@@ -94,7 +94,7 @@ config XGENE_PMU
config ARM_SPE_PMU
tristate "Enable support for the ARMv8.2 Statistical Profiling Extension"
- depends on PERF_EVENTS && ARM64
+ depends on ARM64
help
Enable perf support for the ARMv8.2 Statistical Profiling
Extension, which provides periodic sampling of operations in
--
1.9.1
next reply other threads:[~2018-05-22 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 15:54 John Garry [this message]
2018-05-22 16:08 ` [PATCH] drivers/perf: Remove ARM_SPE_PMU explicit PERF_EVENTS dependency Mark Rutland
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=1527004444-239462-1-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.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