linux-alpha.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-arch@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>, Guo Ren <guoren@kernel.org>,
	linux-alpha@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Michal Simek <monstr@monstr.eu>,
	Max Filippov <jcmvbkbc@gmail.com>,
	Jonas Bonn <jonas@southpole.se>
Subject: [PATCH 1/6] csky: remove BS check for FAULT_FLAG_ALLOW_RETRY
Date: Thu, 11 Sep 2025 02:52:23 +0100	[thread overview]
Message-ID: <20250911015223.GA2604499@ZenIV> (raw)
In-Reply-To: <20250911015124.GV31600@ZenIV>

flags are initialized as FAULT_FLAG_DEFAULT, and the only thing done
to that afterwards is |=; since FAULT_FLAG_DEFAULT already includes
FAULT_FLAG_ALLOW_RETRY, it's guaranteed to remain there all along.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
---
 arch/csky/mm/fault.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/csky/mm/fault.c b/arch/csky/mm/fault.c
index a885518ce1dd..a6ca7dff4215 100644
--- a/arch/csky/mm/fault.c
+++ b/arch/csky/mm/fault.c
@@ -277,7 +277,7 @@ asmlinkage void do_page_fault(struct pt_regs *regs)
 	if (fault & VM_FAULT_COMPLETED)
 		return;
 
-	if (unlikely((fault & VM_FAULT_RETRY) && (flags & FAULT_FLAG_ALLOW_RETRY))) {
+	if (unlikely(fault & VM_FAULT_RETRY)) {
 		flags |= FAULT_FLAG_TRIED;
 
 		/*
-- 
2.47.2


  reply	other threads:[~2025-09-11  1:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11  1:51 [PATCHES] misc dead code removals in arch/* - mostly asm/pgtable.h Al Viro
2025-09-11  1:52 ` Al Viro [this message]
2025-09-11  2:55   ` [PATCH 1/6] csky: remove BS check for FAULT_FLAG_ALLOW_RETRY Guo Ren
2025-09-11  1:53 ` [PATCH 2/6][alpha,m68k,openrisc] PAGE_PTR() had been last used outside of arch/* in 1.1.94 Al Viro
2025-09-11  7:29   ` Geert Uytterhoeven
2025-09-11  1:53 ` [PATCH 3/6][openrisc] SET_PAGE_DIR() users had been gone since 2.3.12pre1 Al Viro
2025-09-11  1:54 ` [PATCH 4/6] alpha: get rid of the remnants of BAD_PAGE and friends Al Viro
2025-09-11  1:54 ` [PATCH 5/6][microblaze,xtensa] kill FIRST_USER_PGD_NR Al Viro
2025-09-11 14:57   ` Max Filippov
2025-09-15  6:42   ` Michal Simek
2025-09-11  1:55 ` [PATCH 6/6] alpha: unobfuscate _PAGE_P() definition Al Viro

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=20250911015223.GA2604499@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --cc=guoren@kernel.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=jonas@southpole.se \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=monstr@monstr.eu \
    /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).