From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: 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: Thu, 27 Jan 2022 09:10:13 +0100 [thread overview]
Message-ID: <20220127081013.GA6362@alpha.franken.de> (raw)
In-Reply-To: <20220125141946.54114-1-tsbogend@alpha.franken.de>
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>
> ---
> arch/mips/include/asm/asm.h | 4 +-
> arch/mips/include/asm/ftrace.h | 4 +-
> arch/mips/include/asm/r4kcache.h | 4 +-
> arch/mips/include/asm/unaligned-emul.h | 176 ++++++++++++-------------
> arch/mips/kernel/mips-r2-to-r6-emul.c | 104 +++++++--------
> arch/mips/kernel/r2300_fpu.S | 6 +-
> arch/mips/kernel/r4k_fpu.S | 2 +-
> arch/mips/kernel/relocate_kernel.S | 22 ++--
> arch/mips/kernel/scall32-o32.S | 10 +-
> arch/mips/kernel/scall64-n32.S | 2 +-
> arch/mips/kernel/scall64-n64.S | 2 +-
> arch/mips/kernel/scall64-o32.S | 10 +-
> arch/mips/kernel/syscall.c | 8 +-
> arch/mips/lib/csum_partial.S | 4 +-
> arch/mips/lib/memcpy.S | 4 +-
> arch/mips/lib/memset.S | 2 +-
> arch/mips/lib/strncpy_user.S | 4 +-
> arch/mips/lib/strnlen_user.S | 2 +-
> 18 files changed, 185 insertions(+), 185 deletions(-)
applied to mips-fixes.
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-27 8:35 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 [this message]
2022-01-30 16:37 ` Guenter Roeck
2022-01-31 10:08 ` Thomas Bogendoerfer
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=20220127081013.GA6362@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.