From: Miles Bader <miles@lsi.nec.co.jp>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: torvalds@transmeta.com, rth@twiddle.net,
linux-kernel@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
ak@suse.de, davem@redhat.com, paulus@samba.org,
rmk@arm.linux.org.uk
Subject: Re: [PATCH] Modules 3/3: Sort sections
Date: 06 Jan 2003 18:25:26 +0900 [thread overview]
Message-ID: <buo3co6bpfd.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <20030102030044.D066C2C05E@lists.samba.org>
The declaration of `module_frob_arch_sections' in moduleloader.h (and
the definitions in most of the module.c files) are inconsistent with the
definition in the PPC's module.c -- in the latter the first two
arguments are not declared `const', whereas everyplace else they are.
I copied the PPC version of module_frob_arch_sections for the v850, and
couldn't compile without changing the type-signature to match. Making
all args const to agree with the declaration results in these warnings:
arch/v850/kernel/module.c: In function `module_frob_arch_sections':
arch/v850/kernel/module.c:124: warning: assignment of read-only member `sh_size'arch/v850/kernel/module.c:126: warning: assignment of read-only member `sh_size'
Since the purpose of module_frob_arch_sections is to frob, perhaps it
makes sense to have the frobable arguments be non-const (in this case
only sechdrs needs it, I guess)... :-)
-Miles
--
"Whatever you do will be insignificant, but it is very important that
you do it." Mahatma Ghandi
next prev parent reply other threads:[~2003-01-06 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 3:00 Rusty Russell
2003-01-02 4:54 ` Richard Henderson
2003-01-02 4:50 ` David S. Miller
2003-01-02 4:58 ` Richard Henderson
2003-01-02 5:15 ` David S. Miller
2003-01-02 10:35 ` Rusty Russell
2003-01-02 17:39 ` Alan Cox
2003-01-02 9:36 ` Arjan van de Ven
2003-01-02 9:37 ` Richard Henderson
2003-01-02 10:48 ` Rusty Russell
2003-01-06 9:25 ` Miles Bader [this message]
2003-01-06 10:17 ` 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=buo3co6bpfd.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.org \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
--cc=rth@twiddle.net \
--cc=rusty@rustcorp.com.au \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@transmeta.com \
/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®