From: "ye janboe" <janboe.ye@gmail.com>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]kbuild: add arm, mips and i386 macros
Date: Wed, 16 Apr 2008 11:10:31 +0800 [thread overview]
Message-ID: <af3ea28a0804152010g5a234640o94f39bbecf0d4637@mail.gmail.com> (raw)
In-Reply-To: <af3ea28a0804092038q59a5b907ndb3d9fa33a6be834@mail.gmail.com>
No one think this patch is needed?
2008/4/10, ye janboe <janboe.ye@gmail.com>:
> commit a80cc2fe14ce7e7a6de70b5927b9c0a6ee530805
> Author: janboe <janboe.ye@gmail.com>
> Date: Thu Apr 10 11:18:03 2008 +0800
>
> the commits 56a974fa2d595fe6ebe433c525b8232ead539b76 and
> ae4ac12323c0ff80528cac3269151d580e23f923
> involved additional macros but not available on cygwin.
> Signed-off-by: Janboe Ye <janboe.ye@gmail.com>
> diff --git a/scripts/mod/modpost.h b/scripts/mod/modpost.h
> index 09f58e3..f864ab8 100644
> --- a/scripts/mod/modpost.h
> +++ b/scripts/mod/modpost.h
> @@ -42,6 +42,16 @@
> #define ELF_R_SYM ELF64_R_SYM
> #define ELF_R_TYPE ELF64_R_TYPE
> #endif
> +#define R_386_32 1 /* Direct 32 bit */
> +#define R_386_PC32 2 /* PC relative 32 bit */
> +
> +#define R_ARM_PC24 1 /* PC relative 26 bit branch */
> +#define R_ARM_ABS32 2 /* Direct 32 bit */
> +
> +#define R_MIPS_32 2 /* Direct 32 bit */
> +#define R_MIPS_26 4 /* Direct 26 bit shifted */
> +#define R_MIPS_HI16 5 /* High 16 bit */
> +#define R_MIPS_LO16 6 /* Low 16 bit */
>
> /* The 64-bit MIPS ELF ABI uses an unusual reloc format. */
> typedef struct
>
next prev parent reply other threads:[~2008-04-16 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 3:38 [PATCH]kbuild: add arm, mips and i386 macros ye janboe
2008-04-16 3:10 ` ye janboe [this message]
2008-04-16 7:55 ` Sam Ravnborg
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=af3ea28a0804152010g5a234640o94f39bbecf0d4637@mail.gmail.com \
--to=janboe.ye@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox