From: Khalid Ali <khaliidcaliy@gmail.com>
To: tglx@linutronix.de, peterz@infradead.org, luto@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/entry: Remove some redundancy checks on syscall
Date: Sun, 15 Jun 2025 08:39:57 +0000 [thread overview]
Message-ID: <20250615084009.906-1-khaliidcaliy@gmail.com> (raw)
In-Reply-To: <87frg2q1w7.ffs@tglx>
Since there were no much objection here i think we agreed with that, so i sent v2
for this one. Could you please redirect our conversasion there. This patch was wrong
so i took your last suggestion and improved it.
Thanks for your patience,
Khalid Ali
prev parent reply other threads:[~2025-06-15 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 20:28 [PATCH] kernel/entry: Remove some redundancy checks on syscall works Khalid Ali
2025-06-14 6:21 ` Thomas Gleixner
2025-06-14 12:04 ` [PATCH] include/linux: Fix outdated comment on entry-common.h Khalid Ali
2025-06-15 8:39 ` Khalid Ali [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=20250615084009.906-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).