mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arthur Naseef" <arthur.naseef@ariel.com>
To: "Keith Owens" <kaos@ocs.com.au>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: RE: Exporting new functions from kernel 2.2.14
Date: Tue, 5 Jun 2001 09:25:55 -0400	[thread overview]
Message-ID: <OIBBKHIAILDFLNOGGFMNIEHMCBAA.arthur.naseef@ariel.com> (raw)
In-Reply-To: <16891.991747473@ocs3.ocs-net>

Thanks for being so helpful. Indeed!

> -----Original Message-----
> From: Keith Owens [mailto:kaos@ocs.com.au]
> Sent: Tuesday, June 05, 2001 9:25 AM
> To: Arthur Naseef
> Cc: Linux Kernel
> Subject: Re: Exporting new functions from kernel 2.2.14 
> 
> 
> On Tue, 5 Jun 2001 09:10:56 -0400, 
> "Arthur Naseef" <arthur.naseef@ariel.com> wrote:
> >I still have not figured out the magic that creates the .ver files which
> >would resolve your concern with the symbol versions, but I do know that
> >you can edit the .ver file yourself (under /usr/src/linux/include/modules/)
> >and add entries.  This will eliminate the funny versioning, as in:
> >
> >    grab_timer_interrupt_R__ver_grab_timer_interrupt
> >
> >You can pick a hash value to use.  For example, you might add the following:
> >
> >	#define __ver_grab_timer_interrupt	a1b2c3d4
> >	#define grab_timer_interrupt	_set_ver(grab_timer_interrupt)
> 
> Remind me _NEVER_ to answer any of your module problems.  Make up your
> own hash indeed, complete and utter rubbish!

  reply	other threads:[~2001-06-05 13:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-05 15:54 Stephen Wille Padnos
2001-06-05 13:10 ` Arthur Naseef
2001-06-05 13:24   ` Keith Owens
2001-06-05 13:25     ` Arthur Naseef [this message]
2001-06-05 17:09   ` Stephen Wille Padnos
2001-06-05 17:32     ` Stephen Wille Padnos
2001-06-05 14:59       ` Keith Owens
2001-06-05 13:23 ` Keith Owens
2001-06-05 17:10   ` Stephen Wille Padnos
2001-06-05 14:22     ` Keith Owens

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=OIBBKHIAILDFLNOGGFMNIEHMCBAA.arthur.naseef@ariel.com \
    --to=arthur.naseef@ariel.com \
    --cc=kaos@ocs.com.au \
    --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
all inboxes | Powered by JetHome®