From: Keith Owens <kaos@sgi.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Michael Frank <mhf@linuxmail.org>,
linux-kernel@vger.kernel.org,
SoftwareSuspend Development
<softwaresuspend-devel@lists.berlios.de>
Subject: Re: [PATCH 2.6.9] KDB: Fix compile problem when CONFIG_KPROBES and CONFIG_KDB set
Date: Tue, 30 Nov 2004 13:31:10 +1100 [thread overview]
Message-ID: <10051.1101781870@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 29 Nov 2004 12:09:48 PDT." <20041129190948.GH22325@smtp.west.cox.net>
On Mon, 29 Nov 2004 12:09:48 -0700,
Tom Rini <trini@kernel.crashing.org> wrote:
>On Sun, Nov 28, 2004 at 04:18:46AM +0800, Michael Frank wrote:
>
>> Both kprobes and kdb defined function do_int3.
>> Both functions were merged.
>
>Is there a reason KDB (or KPROBES for that matter) can't use the notifyr
>chain? That's what KGDB does...
It's on my todo list for kdb v4.5.
prev parent reply other threads:[~2004-11-30 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 20:18 [PATCH 2.6.9] KDB: Fix compile problem when CONFIG_KPROBES and CONFIG_KDB set Michael Frank
2004-11-29 19:09 ` Tom Rini
2004-11-30 2:31 ` Keith Owens [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=10051.1101781870@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.org \
--cc=softwaresuspend-devel@lists.berlios.de \
--cc=trini@kernel.crashing.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