From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Fix build error due to PTR used in more places
Date: Mon, 31 Jan 2022 11:08:45 +0100 [thread overview]
Message-ID: <20220131100845.GA19252@alpha.franken.de> (raw)
In-Reply-To: <20220130163725.GA2792319@roeck-us.net>
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@alpha.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 ]
next prev parent reply other threads:[~2022-01-31 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 14:19 [PATCH] MIPS: Fix build error due to PTR used in more places Thomas Bogendoerfer
2022-01-27 8:10 ` Thomas Bogendoerfer
2022-01-30 16:37 ` Guenter Roeck
2022-01-31 10:08 ` Thomas Bogendoerfer [this message]
2022-02-04 9:26 ` Thorsten Leemhuis
2022-02-04 10:00 ` Thorsten Leemhuis
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=20220131100845.GA19252@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).