From: "ananth at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug uprobes/4738] UPROBES_SSOL and URETPROBES must depend on UPROBES in Kconfig
Date: Mon, 09 Jul 2007 04:16:00 -0000 [thread overview]
Message-ID: <20070709041629.13160.qmail@sourceware.org> (raw)
In-Reply-To: <20070704064428.4738.ananth@in.ibm.com>
------- Additional Comments From ananth at in dot ibm dot com 2007-07-09 04:16 -------
In which case, we have one of two choices:
a> Make the dependency implicit as we do with kprobes (no KPROBES=y implies no
kretprobes either); this will require that we don't touch the Kconfig files,
except to add CONFIG_UPROBES.
b> If you want to retain the Kconfig entries for SSOL and URETPROBES, put in an
explicit dependency for the two on UPROBES. Per Kconfig language semantics, you
shouldn't be able to select a dependent feature without an explicit dependency
specified in the Kconfig file.
Need to choose one; You can't have both :-)
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4738
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-07-09 4:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 6:44 [Bug uprobes/4738] New: " ananth at in dot ibm dot com
2007-07-07 0:16 ` [Bug uprobes/4738] " jkenisto at us dot ibm dot com
2007-07-09 4:16 ` ananth at in dot ibm dot com [this message]
2007-07-09 20:52 ` jkenisto at us dot ibm dot com
2007-07-10 4:53 ` ananth at in dot ibm dot com
2007-07-10 21:01 ` jkenisto at us dot ibm dot com
2007-07-10 21:11 ` fche at redhat dot com
2007-07-10 22:21 ` jkenisto at us dot ibm dot com
2007-07-11 0:42 ` fche at redhat dot com
2007-07-11 4:19 ` ananth at in dot ibm dot com
2007-07-11 17:25 ` jkenisto at us dot ibm dot com
2007-07-11 18:30 ` jkenisto at us dot ibm dot com
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=20070709041629.13160.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).