All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: "kbuild-devel@lists.sourceforge.net" 
	<kbuild-devel@lists.sourceforge.net>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] External kernel modules
Date: Mon, 2 Feb 2004 07:30:42 +0100	[thread overview]
Message-ID: <20040202063042.GA2133@mars.ravnborg.org> (raw)
In-Reply-To: <1075701681.8018.66.camel@nb.suse.de>

On Mon, Feb 02, 2004 at 07:01:21AM +0100, Andreas Gruenbacher wrote:
> I propose the attached patch: It adds symbol version dump/load
> functionality to modpost: When compiling the kernel, the module versions
> are dumped to a file. When compiling external modules, the dumped
> symbols are first loaded. Also, to allow a read-only kernel source tree
> and not interfere with the kernel sources, the .tmp_versions/ directory
> is placed in the external module's directory.
> 
> Furthermore, the patch adds clean/distclean/mrproper make targets with
> reasonable semantics for external modules, and also adds a modules_add
> target that installs the external modules into
> /lib/modules/$(KERNELRELEASE). (The modules_install target could be
> used, but it has different semantics, so I have used a different name
> instead.)

Thanks, I will take a closer look during the week.
Did you consider using the make O=dir support, so .tmp_versions were
created in the output directory?

	Sam

      reply	other threads:[~2004-02-02  6:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02  6:01 [RFC] External kernel modules Andreas Gruenbacher
2004-02-02  6:30 ` Sam Ravnborg [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=20040202063042.GA2133@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=agruen@suse.de \
    --cc=kbuild-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.