mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Levon <movement@marcelothewonderpenguin.com>
To: Nick Popoff <lkml@tre.bloodletting.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question regarding do_munmap
Date: Tue, 4 Jun 2002 19:44:07 +0100	[thread overview]
Message-ID: <20020604184407.GA63233@compsoc.man.ac.uk> (raw)
In-Reply-To: <153.25.1023215073895@tre.bloodletting.com>

On Tue, Jun 04, 2002 at 11:24:33AM -0700, Nick Popoff wrote:

> (Generic 2.4.18 include/linux/mm.h) 
> extern int do_munmap(struct mm_struct *, unsigned long, size_t); 
>  
> (RH 7.3/AC patched 2.4.18-3 include/linux/mm.h) 
> extern int do_munmap(struct mm_struct *, unsigned long, size_t, int 
> acct); 
>  
> My question is what is the recommended way for module developers to 
> handle changes to this API so that end users don't have to edit 
> makefiles to build for their particular kernel?  Is there a way to 

Add some tests in a ./configure script that finds out which one
is being used in the kernel headers.

> how to handle this besides grep'ing source in my installer? :-) 

It's roughly similar to this though. API creep is one of the facts of
external module development on Linux, I'm afraid.

regards
john

-- 
"Do you mean to tell me that "The Prince" is not the set textbook for CS1072
Professional Issues ? What on earth do you learn in that course ?"
	- David Lester

  reply	other threads:[~2002-06-04 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 18:24 Nick Popoff
2002-06-04 18:44 ` John Levon [this message]
2002-06-04 20:27 ` Alan Cox

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=20020604184407.GA63233@compsoc.man.ac.uk \
    --to=movement@marcelothewonderpenguin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@tre.bloodletting.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

all inboxes | Powered by JetHome®