All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: sam@ravnborg.org, kbuid-devel@lists.sourceforge.net
Subject: Re: [PATCH] [KBUILD] fix external module install path
Date: Mon, 07 May 2007 17:15:34 -0500	[thread overview]
Message-ID: <463FA506.3070207@redhat.com> (raw)
In-Reply-To: <463F9DFF.7010101@redhat.com>

Eric Sandeen wrote:
> Eric Sandeen wrote:
>> Installing external modules is supposed to put them in some path
>> under /lib/modules/<version>/extra/subdir/, but this change:
>> http://linux.bkbits.net:8080/linux-2.6/?PAGE=cset&REV=1.1982.9.23
>> makes them go under /lib/modules/<version>/extrasubdir
> 
> er, hang on.  Now it's not doing it ;-)  stay tuned.
> 
> Sorry... I really did get an "extrafs/" directory somehow :)

Urgh, I can't figure out what tickles it reliably.

There is at least another buglet (?) though, if you don't put a slash on
the end of your M=, you lose the subdir path.

[root@marathon-01 linux-2.6.18.x86_64]# make M=fs/ext3/ modules_install
  INSTALL fs/ext3/ext3.ko
  DEPMOD  2.6.18-8.el5
[root@marathon-01 linux-2.6.18.x86_64]# find /lib/modules/`uname
-r`/extra* -name ext3.ko
/lib/modules/2.6.18-8.el5/extra/fs/ext3/ext3.ko

[root@marathon-01 linux-2.6.18.x86_64]# make M=fs/ext3 modules_install
  INSTALL fs/ext3/ext3.ko
  DEPMOD  2.6.18-8.el5
[root@marathon-01 linux-2.6.18.x86_64]# find /lib/modules/`uname
-r`/extra* -name ext3.ko
/lib/modules/2.6.18-8.el5/extra/fs/ext3/ext3.ko
/lib/modules/2.6.18-8.el5/extra/ext3.ko

I'm confused.  Maybe Sam knows how to fix it... :)

-Eric

  reply	other threads:[~2007-05-07 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 21:38 [PATCH] [KBUILD] fix external module install path Eric Sandeen
2007-05-07 21:45 ` Eric Sandeen
2007-05-07 22:15   ` Eric Sandeen [this message]
2008-01-01 12:45 ` Sam Ravnborg
2008-01-01 17:10   ` Eric Sandeen

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=463FA506.3070207@redhat.com \
    --to=sandeen@redhat.com \
    --cc=kbuid-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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.