From: Thomas Gleixner <tglx@linutronix.de>
To: Khalid Ali <khaliidcaliy@gmail.com>,
peterz@infradead.org, luto@kernel.org,
linux-kernel@vger.kernel.org
Cc: Khalid Ali <khaliidcaliy@gmail.com>
Subject: Re: [PATCH] kernel/entry: Fix misleading comment in irqentry_enter()
Date: Mon, 16 Jun 2025 09:08:16 +0200 [thread overview]
Message-ID: <87msa8noyn.ffs@tglx> (raw)
In-Reply-To: <20250614192729.10760-1-khaliidcaliy@gmail.com>
On Sat, Jun 14 2025 at 19:26, Khalid Ali wrote:
> Change irqentry_enter_from_user_mode() to enter_from_user_mode(),
> because enter_from_user_mode() function is the one doing the action
> comment indicates.
irqentry_enter_from_user_mode() is what is called in the user entry
branch, so the comment is not misleading at all. If someone can't follow
that function and figure out that it calls enter_from_user_mode() so be
it.
Thanks,
tglx
prev parent reply other threads:[~2025-06-16 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 19:26 [PATCH] kernel/entry: Fix misleading comment in irqentry_enter() Khalid Ali
2025-06-16 7:08 ` 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=87msa8noyn.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