[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220131100845.GA19252@alpha.franken.de>
Date: Mon, 31 Jan 2022 11:08:45 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MIPS: Fix build error due to PTR used in more places
On Sun, Jan 30, 2022 at 08:37:25AM -0800, Guenter Roeck wrote:
> On Tue, Jan 25, 2022 at 03:19:44PM +0100, Thomas Bogendoerfer wrote:
> > Use PTR_WD instead of PTR to avoid clashes with other parts.
> >
> > Signed-off-by: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
>
> Building mips:cavium_octeon_defconfig ... failed
> --------------
> Error log:
> arch/mips/cavium-octeon/octeon-memcpy.S: Assembler messages:
> arch/mips/cavium-octeon/octeon-memcpy.S:187: Error: unrecognized opcode `ptr 9b,l_exc'
> ...
>
> Missed one place in Cavium assembler code.
>
> arch/mips/cavium-octeon/octeon-memcpy.S: PTR 9b, handler;
>
> #regzbot introduced: fa62f39dc7e2
d'oh, fix sent.
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