From: Keith Owens <kaos@ocs.com.au>
To: sacx@zebra.sibnet.ro
Cc: linux-kernel@vger.kernel.org
Subject: Re: module
Date: Tue, 28 Aug 2001 09:17:07 +1000 [thread overview]
Message-ID: <3265.998954227@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 27 Aug 2001 18:51:49 -0400." <Pine.LNX.4.33L2.0108271826510.32587-100000@zebra.sibnet.ro>
On Mon, 27 Aug 2001 18:51:49 -0400 (EDT),
<sacx@zebra.sibnet.ro> wrote:
>c027b7f0 function_R__ver_function (# cat /proc/ksyms | grep function)
>P.S. I'm a newbie in kernel hacking and I don't want to disturb you but
Always read the FAQ before asking questions. You will find this
question answered in the lkml FAQ which appears at the end of every
mail on lkml.
next prev parent reply other threads:[~2001-08-27 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 22:51 module sacx
2001-08-27 16:04 ` module John Levon
2001-08-27 23:17 ` Keith Owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-08 11:57 Module Sourav Sen
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=3265.998954227@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sacx@zebra.sibnet.ro \
/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