[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230217115812.GB7701@alpha.franken.de>
Date: Fri, 17 Feb 2023 12:58:12 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: Philippe Mathieu-Daudé <philmd@...aro.org>,
linux-kernel@...r.kernel.org, Song Liu <song@...nel.org>,
Luis Chamberlain <mcgrof@...nel.org>,
linux-mips@...r.kernel.org
Subject: Re: [PATCH] module: fix MIPS module_layout -> module_memory
On Tue, Feb 14, 2023 at 08:52:04AM -0800, Randy Dunlap wrote:
>
>
> On 2/13/23 23:22, Philippe Mathieu-Daudé wrote:
> > Hi Randy,
> >
> > On 14/2/23 01:54, Randy Dunlap wrote:
> >> Correct the struct's field/member name from mod_mem to mem.
> >>
> >> Fixes this build error:
> >> ../arch/mips/kernel/vpe.c: In function 'vpe_elfload':
> >> ../arch/mips/kernel/vpe.c:643:41: error: 'struct module' has no member named 'mod_mem'
> >> 643 | v->load_addr = alloc_progmem(mod.mod_mem[MOD_TEXT].size);
> >>
> >> Fixes: 2ece476a2346 ("module: replace module_layout with module_memory")
> >
> > On which tree is your patch based?
>
> linux-next-20230213.
so I can't apply, because this is not in mips-next tree. It should be
applied to the tree, where this commit is coming from.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists