From: Joakim Hernberg <jhernberg@alchemy.lu>
To: linux-rt-users@vger.kernel.org
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: [PATCH] make HWLAT_DETECTOR kernel config either disabled or a module, never builtin.
Date: Wed, 23 Sep 2015 19:33:40 +0200 [thread overview]
Message-ID: <20150923193340.0881074b@tor.valhalla.alchemy.lu> (raw)
Since the HWLAT_DETECTOR driver supposedly shouldn't be builtin, but a
module when used at all, it would make sense to limit the configuration
choices:
Signed-off-by: Joakim Hernberg <jhernberg@alchemy.lu>
Suggested-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
---
drivers/misc/Kconfig | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 453a616..94756c3 100644
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
@@ -124,8 +124,7 @@ config IBM_ASM
config HWLAT_DETECTOR
tristate "Testing module to detect hardware-induced latencies"
- depends on DEBUG_FS
- depends on RING_BUFFER
+ depends on DEBUG_FS && RING_BUFFER && m
default m
---help---
A simple hardware latency detector. Use this module to detect
--
2.5.3
--
Joakim
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-09-23 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 17:33 Joakim Hernberg [this message]
2015-12-11 16:52 ` [PATCH] make HWLAT_DETECTOR kernel config either disabled or a module, never builtin Sebastian Andrzej Siewior
2015-12-11 19:47 ` Joakim Hernberg
2015-12-13 10:39 ` Joakim Hernberg
2015-12-22 15:11 ` Sebastian Andrzej Siewior
2015-12-22 16:25 ` John Kacur
2015-12-22 16:34 ` Sebastian Andrzej Siewior
2015-12-22 16:43 ` John Kacur
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=20150923193340.0881074b@tor.valhalla.alchemy.lu \
--to=jhernberg@alchemy.lu \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).