mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jari Ruusu <jariruusu@users.sourceforge.net>
Cc: linux-crypto@nl.linux.org, linux-kernel@vger.kernel.org
Subject: Re: Announce loop-AES-v3.1c file/swap crypto package
Date: Sat, 28 Jan 2006 23:57:25 +0100	[thread overview]
Message-ID: <20060128225725.GA18727@mars.ravnborg.org> (raw)
In-Reply-To: <43D260F8.B82BCB9A@users.sourceforge.net>

On Sat, Jan 21, 2006 at 06:27:36PM +0200, Jari Ruusu wrote:
> Sam Ravnborg wrote:
> > Either something is missing in the support for external modules in the
> > kernel or you are overdoing some stuff. If there is something missing in
> > the kernel to support external modules then please say so, so it can be
> > fixed.
> 
> Missing functionality:
> 1) "make M=/path/to/dir modules_install" does not run depmod. Pulling
>    correct depmod info from kernel Makefile needs ugly hacks.
Fixed in latest kbuild.
One day I need to get full grip on the module-init-tools stuff....

> 2) Try building external module A that exports some function, and then build
>    another external module B (separate package, only knows function
>    prototype) that uses said exported function. And I mean build it cleanly
>    without puking error messages on me. 2.4 and older kernel got that right,
>    but 2.6 is still FUBAR. Serious regression here.
This was always possible using a kbuild file specifying all relevant
modules. But accepting this is not always doable kbuild now add an
additional method.
build module a
copy Module.symvers from module a to module b.
Voila, module b has full access to symbols from module a. This includes
module versioning support.
Both methods are documented in Documentation/kbuild/modules.txt now.


Both changes are in my kbuild.git tree and I will send out a series of
patches to lkml soon. It will be available for testing in next -mm too.

Thanks for input, and please let me know if you know of more
shortcomings in kbuild that needs to be addressed.

	Sam

  parent reply	other threads:[~2006-01-28 22:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 15:49 Jari Ruusu
2006-01-20 19:50 ` Sam Ravnborg
2006-01-21 16:27   ` Jari Ruusu
2006-01-21 22:10     ` Sam Ravnborg
2006-01-28 22:57     ` Sam Ravnborg [this message]
2006-01-29 14:47       ` Jari Ruusu

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=20060128225725.GA18727@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=jariruusu@users.sourceforge.net \
    --cc=linux-crypto@nl.linux.org \
    --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®