From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2312] Built failure when CONFIG_MODULES disabled
Date: Thu, 09 Feb 2006 18:23:00 -0000 [thread overview]
Message-ID: <20060209182341.26828.qmail@sourceware.org> (raw)
In-Reply-To: <20060209174527.2312.anil.s.keshavamurthy@intel.com>
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|systemtap at sources dot |anil dot s dot keshavamurthy
|redhat dot com |at intel dot com
Status|NEW |ASSIGNED
http://sourceware.org/bugzilla/show_bug.cgi?id=2312
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2006-02-09 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 17:45 [Bug kprobes/2312] New: " anil dot s dot keshavamurthy at intel dot com
2006-02-09 18:23 ` jkenisto at us dot ibm dot com [this message]
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=20060209182341.26828.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).