[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZhgG5fxCEmo6gnVs@antec>
Date: Thu, 11 Apr 2024 16:51:01 +0100
From: Stafford Horne <shorne@...il.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Jonas Bonn <jonas@...thpole.se>,
Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>,
Eric Biederman <ebiederm@...ssion.com>,
Kees Cook <keescook@...omium.org>, linux-openrisc@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH] openrisc: Add support for more module relocations
On Thu, Apr 11, 2024 at 02:12:59PM +0200, Geert Uytterhoeven wrote:
> Hi Stafford,
>
> On Wed, Apr 10, 2024 at 10:52 PM Stafford Horne <shorne@...il.com> wrote:
> > This patch adds the relocations. Note, we use the old naming R_OR32_*
> > instead or the new naming R_OR1K_* to avoid change as this header is
> > exported as a user api.
>
> > --- a/arch/openrisc/include/uapi/asm/elf.h
> > +++ b/arch/openrisc/include/uapi/asm/elf.h
> > @@ -43,6 +43,8 @@
> > #define R_OR32_JUMPTARG 6
> > #define R_OR32_VTINHERIT 7
> > #define R_OR32_VTENTRY 8
> > +#define R_OR32_AHI16 35
> > +#define R_OR32_SLO16 39
>
> Would it make sense to switch to the new names, e.g.
>
> #define R_OR1K_NONE 0
>
> and add definitions for backwards compatibility?
>
> #define R_OR32_NONE R_OR1K_NONE
>
Hi Geert,
Actually I had a patch doing this and added all 38 or so relocation definitions.
But I dropped it at the last moment in favor of simplicity.
Let me rework it and add it back.
-Stafford
Powered by blists - more mailing lists