From: Rusty Lynch <rusty@linux.intel.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: recent kprobe work
Date: Tue, 28 Jun 2005 14:40:06 -0700 [thread overview]
Message-ID: <20050628214006.GA19157@linux.jf.intel.com> (raw)
In-Reply-To: <20050628.140136.57453291.davem@davemloft.net>
On Tue, Jun 28, 2005 at 02:01:36PM -0700, David S. Miller wrote:
>
> Can the folks submitting all of the kprobe stuff at least consult me
> when they can't figure out how to implement the sparc64 kprobe variant
> for new features?
>
> Currently, the sparc64 build is broken by recent kprobe
> changes:
>
> kernel/built-in.o: In function `init_kprobes':
> : undefined reference to `arch_init'
>
> Also, can we use a more namespace friendly name for this kprobe layer
> specific function other than "arch_init()"?
>
> Thanks.
Sorry, just an oversight. We have several arch_* functions, maybe we should
start using kprobes_arch_* instead.
--rusty
next prev parent reply other threads:[~2005-06-28 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 21:01 recent kprobe work David S. Miller
2005-06-28 21:40 ` Rusty Lynch [this message]
2005-06-29 0:50 ` Andrew Morton
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=20050628214006.GA19157@linux.jf.intel.com \
--to=rusty@linux.intel.com \
--cc=davem@davemloft.net \
--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