The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Khalid Ali <khaliidcaliy@gmail.com>,
	peterz@infradead.org, luto@kernel.org
Cc: linux-kernel@vger.kernel.org, Khalid Ali <khaliidcaliy@gmail.com>
Subject: Re: [PATCH v2] entry: Update outdated comment in entry_common.h
Date: Fri, 20 Jun 2025 23:14:59 +0200	[thread overview]
Message-ID: <87pleyp12k.ffs@tglx> (raw)
In-Reply-To: <20250618081305.1060-1-khaliidcaliy@gmail.com>

On Wed, Jun 18 2025 at 08:12, Khalid Ali wrote:

$Subject: entry: Update outdated kernel doc for syscall_trace_enter()

The shortlog should describe the change concisely. 'in entry_common.h'
tells absolutely nothing.

> From: Khalid Ali <khaliidcaliy@gmail.com>
>
> The comment above syscall_enter_from_user_mode() refers to
> syscall_enter_from_user_mode_prepare(), which is no longer used. This can
> mislead readers trying to follow the entry path.
>
> Update the comment to reflect the current implementation by replacing
> syscall_enter_from_user_mode_prepare() with enter_from_user_mode().
>
> Signed-off-by: Khalid Ali <khaliidcaliy@gmail.com>
> ---
>  include/linux/entry-common.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/entry-common.h b/include/linux/entry-common.h
> index dad1f257e3dd..49f5d99b254c 100644
> --- a/include/linux/entry-common.h
> +++ b/include/linux/entry-common.h
> @@ -146,7 +146,7 @@ long syscall_trace_enter(struct pt_regs *regs, long syscall,
>   * @syscall:	The syscall number
>   *
>   * Invoked from architecture specific syscall entry code with interrupts
> - * enabled after invoking syscall_enter_from_user_mode_prepare() and extra
> + * enabled after invoking enter_from_user_mode() and extra
>   * architecture specific work.

And how is that more correct? I explained it to you in great detail what
the prerequisites are:

 https://lore.kernel.org/all/87cyb6q1aj.ffs@tglx

No?

Thanks,

        tglx

      reply	other threads:[~2025-06-20 21:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18  8:12 [PATCH v2] entry: Update outdated comment in entry_common.h Khalid Ali
2025-06-20 21:14 ` Thomas Gleixner [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=87pleyp12k.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=khaliidcaliy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.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