From: Khalid Ali <khaliidcaliy@gmail.com>
To: tglx@linutronix.de, peterz@infradead.org, luto@kernel.org
Cc: linux-kernel@vger.kernel.org, Khalid Ali <khaliidcaliy@gmail.com>
Subject: [PATCH] kernel/entry: Remove duplicate function documentation
Date: Sun, 15 Jun 2025 12:04:26 +0000 [thread overview]
Message-ID: <20250615120429.1496-1-khaliidcaliy@gmail.com> (raw)
Move exit_to_user_mode_loop() documentation to "entry-common.h",
above function prototype for consistency and remove duplicate
function doc.
Signed-off-by: Khalid Ali <khaliidcaliy@gmail.com>
---
include/linux/entry-common.h | 2 ++
kernel/entry/common.c | 5 -----
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/include/linux/entry-common.h b/include/linux/entry-common.h
index f94f3fdf15fc..dad1f257e3dd 100644
--- a/include/linux/entry-common.h
+++ b/include/linux/entry-common.h
@@ -302,6 +302,8 @@ void arch_do_signal_or_restart(struct pt_regs *regs);
/**
* exit_to_user_mode_loop - do any pending work before leaving to user space
+ * @regs: Pointer to pt_regs on entry stack
+ * @ti_work: TIF work flags as read by the caller
*/
unsigned long exit_to_user_mode_loop(struct pt_regs *regs,
unsigned long ti_work);
diff --git a/kernel/entry/common.c b/kernel/entry/common.c
index 3e9f2d40230f..67df77732fd2 100644
--- a/kernel/entry/common.c
+++ b/kernel/entry/common.c
@@ -81,11 +81,6 @@ noinstr void syscall_enter_from_user_mode_prepare(struct pt_regs *regs)
/* Workaround to allow gradual conversion of architecture code */
void __weak arch_do_signal_or_restart(struct pt_regs *regs) { }
-/**
- * exit_to_user_mode_loop - do any pending work before leaving to user space
- * @regs: Pointer to pt_regs on entry stack
- * @ti_work: TIF work flags as read by the caller
- */
__always_inline unsigned long exit_to_user_mode_loop(struct pt_regs *regs,
unsigned long ti_work)
{
--
2.49.0
next reply other threads:[~2025-06-15 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 12:04 Khalid Ali [this message]
2025-06-20 21:16 ` [PATCH] kernel/entry: Remove duplicate function documentation Thomas Gleixner
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=20250615120429.1496-1-khaliidcaliy@gmail.com \
--to=khaliidcaliy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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).