From: Sam Ravnborg <sam@ravnborg.org>
To: John Levon <levon@movementarian.org>
Cc: Mikael Pettersson <mikpe@csd.uu.se>, linux-kernel@vger.kernel.org
Subject: Re: [2.5] initrd/mkinitrd still not working
Date: Mon, 20 Jan 2003 20:12:50 +0100 [thread overview]
Message-ID: <20030120191250.GA1314@mars.ravnborg.org> (raw)
In-Reply-To: <20030120155250.GB58326@compsoc.man.ac.uk>
On Mon, Jan 20, 2003 at 03:52:50PM +0000, John Levon wrote:
> > As to why the .o -> .ko name change was necessary, I have no idea.
> > Rusty?
>
> For one thing, it means you can do :
>
> obj-$(CONFIG_OPROFILE) += oprofile.o
> oprofile-y := $(DRIVER_OBJS) init.o
> timer_int.o
> oprofile-$(CONFIG_X86_LOCAL_APIC) += nmi_int.o op_model_athlon.o \
> op_model_ppro.o op_model_p4.o
The above mentioned possibility to list 'members' of a composite object
by means of either:
oprofile-y
or
oprofile-objs
has nothing to do with the .ko extension.
But that feature may have been added in the same time-frame though.
I do not recall exactly whay Kai introduced the .ko extension, but
without checking I assume that makes it easier / possible to do some
added tricks in the makefiles.
Sam
next prev parent reply other threads:[~2003-01-20 19:03 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 [this message]
2003-01-20 19:19 ` John Levon
2003-01-20 19:35 ` Sam Ravnborg
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=20030120191250.GA1314@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 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.