From: Sam Ravnborg <sam@ravnborg.org>
To: Kai Germaschewski <kai-germaschewski@uiowa.edu>
Cc: linux-kernel@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [RFC] [PATCH] new modversions implementation
Date: Sat, 25 Jan 2003 22:56:37 +0100 [thread overview]
Message-ID: <20030125215637.GA3571@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0301251229120.6749-100000@chaos.physics.uiowa.edu>
On Sat, Jan 25, 2003 at 12:44:39PM -0600, Kai Germaschewski wrote:
Just some small nit-picking..
Sam
diff -Nru a/kernel/module.c b/kernel/module.c
--- a/kernel/module.c Sat Jan 25 12:25:07 2003
+++ b/kernel/module.c Sat Jan 25 12:25:07 2003
+ kernel_gpl_symbols.num_syms = (__stop___ksymtab_gpl
+ - __start___ksymtab_gpl);
The member "num_syms" says something about number of symbols,
but is contains the syms_size. Misleading name.
I can see this was also the case before, but confused me a bit.
+ | $(GENKSYMS) -k $(VERSION).$(PATCHLEVEL).$(SUBLEVEL) \
+ | grep __ver \
+ | sed 's/\#define __ver_\([^ ]*\)[ ]*\([^ ]*\)/__crc_\1 =
+0x\2 ;/g' \
A genksyms replacement should do all the three steps above?
+cmd_link_multi-m = $(LD) $(LDFLAGS) $(EXTRA_LDFLAGS) $(LDFLAGS_MODULE) -o $@
+$(filter $(addprefix $(obj)/,$($(subst $(obj)/,,$(@:.o=-objs))) $($(subst
+$(obj)/,,$(@:.o=-y)))),$^)
The comment
#
# Rule to link composite objects
#
Could tell a bit more:
#
# Rule to link composite objects
# Listed in kbuild makefiles with:
# <composite object>-objs := <list of .o files>
# or
# <composite object>-y := <list of .o files>
#
+cmd_link_module = $(LD) $(LDFLAGS) $(EXTRA_LDFLAGS) $(LDFLAGS_MODULE) -o $@ $<
+init/vermagic.o
How about
ld_modflags = $(LDFLAGS) $(EXTRA_LDFLAGS) $(LDFLAGS_MODULE)
+
+# Don't rebuilt vermagic.o unless we actually are in the init/ dir
+ifneq ($(obj),init)
+init/vermagic.o: ;
+endif
The above magic does not look safe to me when utilising parrallel builds.
At least init/vermagic.o needs to be in the prepare: rule.
+$(multi-used-m) : %.o: $(multi-objs-m) FORCE
I cannot see the need for the "%.o". The "%" is not used - or have
I misunderstood the usage of the above construction?
+ $(touch-module)
Add comment:
+ $(touch-module) # Record update in .tmp_versions/path/to/module.ko
quiet_cmd_link_multi-m = LD [M] $@
-quiet_cmd_link_single-m = LD [M] $@
+quiet_cmd_link_module = LD [M] $@
Inconsistent naming, I would like the old naming back for consistency.
Sam
next prev parent reply other threads:[~2003-01-25 21:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 18:44 [RFC] [PATCH] new modversions implementation Kai Germaschewski
2003-01-25 21:56 ` Sam Ravnborg [this message]
2003-01-25 22:56 ` Sam Ravnborg
2003-01-26 2:31 ` Kai Germaschewski
2003-01-26 2:30 ` Kai Germaschewski
2003-01-28 7:07 ` Rusty Russell
2003-01-28 16:40 ` Kai Germaschewski
2003-01-28 7:06 ` Rusty Russell
2003-01-28 19:20 ` Sam Ravnborg
2003-01-28 10:38 ` Rusty Russell
2003-01-28 16:31 ` Richard Henderson
2003-01-28 16:35 ` Kai Germaschewski
2003-01-29 0:15 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2003-02-02 8:37 [RFC][PATCH] " Paul Marinceu
2003-02-02 8:51 ` David Woodhouse
2003-02-03 0:46 ` Rusty Russell
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=20030125215637.GA3571@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kai-germaschewski@uiowa.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.