From: Sam Ravnborg <sam@ravnborg.org>
To: John Levon <levon@movementarian.org>
Cc: linux-kernel@vger.kernel.org, Mikael Pettersson <mikpe@csd.uu.se>
Subject: Re: [2.5] initrd/mkinitrd still not working
Date: Mon, 20 Jan 2003 20:35:46 +0100 [thread overview]
Message-ID: <20030120193546.GC1314@mars.ravnborg.org> (raw)
In-Reply-To: <20030120191921.GA84425@compsoc.man.ac.uk>
On Mon, Jan 20, 2003 at 07:19:21PM +0000, John Levon wrote:
> Ooops, I was mis-remembering commit logs. I meant :
>
> http://linus.bkbits.net:8080/linux-2.5/user=kai/cset@1.838.1.86?nav=!-|index.html|stats|!+|index.html|ChangeSet
OK, this is something else.
Making the shift to the extension .ko allowed the syntax:
make fs/ext2/ext2.ko or whatever module we want to build.
Thats very nice when developing on a module to speed up things.
As of today you can actually do:
make fs/ext2/file.o
make fs/ext2/file.lst
make fs/ext2/file.s
make fs/ext2/file.i
and the above mentioned with a .ko module.
There is also the possibility to do:
make SUBDIRS=fs/ext2
and I hope that the following syntax will be anabled as well:
make fs/ext2/
[Patch queued for submission]
Sam
next prev parent reply other threads:[~2003-01-20 19:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 14:57 [2.5] initrd/mkinitrd still not working Mikael Pettersson
2003-01-20 15:52 ` John Levon
2003-01-20 19:12 ` Sam Ravnborg
2003-01-20 19:19 ` John Levon
2003-01-20 19:35 ` Sam Ravnborg [this message]
2003-01-21 2:18 ` Michal Jaegermann
2003-01-21 17:02 ` Bill Davidsen
2003-01-28 1:03 ` Rusty Russell
2003-01-28 17:10 ` Bill Davidsen
2003-01-29 0:48 ` Rusty Russell
2003-01-29 1:56 ` Herbert Xu
2003-01-29 6:21 ` Rusty Russell
2003-02-02 15:28 ` Bill Davidsen
2003-02-03 0:59 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2003-01-18 19:46 Bill Davidsen
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=20030120193546.GC1314@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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