From: Matt Mackall <mpm@selenic.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
karim@opersys.com
Subject: [PATCH] LTT config bits break config tree
Date: Sat, 29 Jan 2005 16:28:48 -0800 [thread overview]
Message-ID: <20050130002848.GD2891@waste.org> (raw)
The LTT option got dropped in the middle of the CONFIG_EMBEDDED menu
without a dependency on EMBEDDED. Selecting EMBEDDED in menuconfig now
causes a bunch of random embedded options to appear on the general
options menu.
Not really sure if this belongs here or in the debugging menus.
Signed-off-by: Matt Mackall <mpm@selenic.com>
Index: tq/init/Kconfig
===================================================================
--- tq.orig/init/Kconfig 2005-01-29 16:17:03.000000000 -0800
+++ tq/init/Kconfig 2005-01-29 16:23:34.000000000 -0800
@@ -324,7 +324,7 @@
config LTT
bool "Linux Trace Toolkit support"
select RELAYFS_FS
- depends on !X86_64
+ depends on !X86_64 && EMBEDDED
default n
---help---
It is possible for the kernel to log important events to a trace
--
Mathematics is the supreme nostalgia of our time.
reply other threads:[~2005-01-30 0:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050130002848.GD2891@waste.org \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.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