From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MIPS: remove asm/war.h
Date: Tue, 22 Feb 2022 09:46:15 +0100 [thread overview]
Message-ID: <20220222084615.GC7049@alpha.franken.de> (raw)
In-Reply-To: <20220218100441.81944-1-tsbogend@alpha.franken.de>
On Fri, Feb 18, 2022 at 11:04:39AM +0100, Thomas Bogendoerfer wrote:
> The major part for workaround handling has already moved to config
> options. This change replaces the remaining defines by already
> available config options and gets rid of war.h
>
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> ---
> arch/mips/Kconfig | 38 ++++++++++++++++
> arch/mips/include/asm/futex.h | 1 -
> arch/mips/include/asm/mipsmtregs.h | 1 -
> arch/mips/include/asm/mipsregs.h | 1 -
> arch/mips/include/asm/war.h | 73 ------------------------------
> arch/mips/kernel/entry.S | 1 -
> arch/mips/kernel/genex.S | 1 -
> arch/mips/kernel/r4k-bugs64.c | 9 ++--
> arch/mips/kernel/scall32-o32.S | 1 -
> arch/mips/kernel/scall64-n64.S | 1 -
> arch/mips/kernel/signal.c | 1 -
> arch/mips/kernel/signal_n32.c | 1 -
> arch/mips/lib/delay.c | 1 -
> arch/mips/mm/c-octeon.c | 1 -
> arch/mips/mm/c-r4k.c | 1 -
> arch/mips/mm/page.c | 5 +-
> arch/mips/mm/tlbex.c | 1 -
> 17 files changed, 47 insertions(+), 91 deletions(-)
> delete mode 100644 arch/mips/include/asm/war.h
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-02-22 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 10:04 [PATCH v2] MIPS: remove asm/war.h Thomas Bogendoerfer
2022-02-22 8:46 ` Thomas Bogendoerfer [this message]
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=20220222084615.GC7049@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.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