From: Andrew Morton <akpm@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
Roman Zippel <zippel@linux-m68k.org>
Subject: Re: [patch 1/2] m68k: runtime patching infrastructure
Date: Tue, 29 May 2007 17:38:18 -0700 [thread overview]
Message-ID: <20070529173818.fd94ae81.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070528191715.352919509@mail.of.borg>
On Mon, 28 May 2007 21:16:31 +0200
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> --- a/include/asm-m68k/module.h
> +++ b/include/asm-m68k/module.h
> @@ -1,7 +1,38 @@
> #ifndef _ASM_M68K_MODULE_H
> #define _ASM_M68K_MODULE_H
> -struct mod_arch_specific { };
> +
> +struct mod_arch_specific {
> + struct m68k_fixup_info *fixup_start, *fixup_end;
> +};
Here we use struct m68k_fixup_info.
> +#define MODULE_ARCH_INIT { \
> + .fixup_start = __start_fixup, \
> + .fixup_end = __stop_fixup, \
> +}
> +
> #define Elf_Shdr Elf32_Shdr
> #define Elf_Sym Elf32_Sym
> #define Elf_Ehdr Elf32_Ehdr
> +
> +
> +enum m68k_fixup_type {
> + m68k_fixup_memoffset,
> +};
> +
> +struct m68k_fixup_info {
> + enum m68k_fixup_type type;
> + void *addr;
> +};
and later we define it.
How come it doesn't spit warnings?
I think it could be tightened up even if it happens not to warn?
> +#define m68k_fixup(type, addr) \
> + " .section \".m68k_fixup\",\"aw\"\n" \
> + " .long " #type "," #addr "\n" \
> + " .previous\n"
> +
> +extern struct m68k_fixup_info __start_fixup[], __stop_fixup[];
> +
> +struct module;
> +extern void module_fixup(struct module *mod, struct m68k_fixup_info *start,
> + struct m68k_fixup_info *end);
next prev parent reply other threads:[~2007-05-30 0:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 19:16 [patch 0/2] A few more m68k patches Geert Uytterhoeven
2007-05-28 19:16 ` [patch 1/2] m68k: runtime patching infrastructure Geert Uytterhoeven
2007-05-30 0:38 ` Andrew Morton [this message]
2007-05-30 5:48 ` Eric Dumazet
2007-05-30 7:06 ` Geert Uytterhoeven
2007-05-30 8:20 ` Joerg Dorchain
2007-05-30 11:19 ` Geert Uytterhoeven
2007-05-30 11:40 ` Joerg Dorchain
2007-05-30 8:23 ` Andreas Schwab
2007-05-30 18:03 ` Linus Torvalds
2007-06-03 15:56 ` Wouter Verhelst
2007-05-28 19:16 ` [patch 2/2] m68k: Discontinuous memory support Geert Uytterhoeven
2007-05-30 0:44 ` Andrew Morton
2007-05-30 0:45 ` Andrew Morton
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=20070529173818.fd94ae81.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zippel@linux-m68k.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.