From: Shuah Khan <skhan@linuxfoundation.org>
To: Sameeksha Sankpal <sameekshasankpal@gmail.com>
Cc: kees@kernel.org, luto@amacapital.net, wad@chromium.org,
shuah@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3] selftests/seccomp: Fix indentation and rebase error logging patch
Date: Tue, 25 Nov 2025 10:25:18 -0700 [thread overview]
Message-ID: <588480bb-f498-400d-8241-6a317709b514@linuxfoundation.org> (raw)
In-Reply-To: <CAGZaOhcmHt76q=ABQ-NJvj9tuedCeonEFGP8SvnhUp9=+T5tPQ@mail.gmail.com>
On 11/24/25 21:04, Sameeksha Sankpal wrote:
> Hi Shuah,
>
> Thanks for pointing that out. Apologies for missing the mailing lists earlier.
> Resending this follow-up with the correct CC list and in plain text format.
>
> Please let me know if there’s anything else I should improve in this patch.
> I’m happy to resend it as v4 if needed.
No top post to start with. Resend v3 for review instead of adding mailing
lists and everybody getmaintainers script suggests.
thanks,
-- Shuah
prev parent reply other threads:[~2025-11-25 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 12:27 [PATCH] selftests/seccomp: report errno and add hints on failure Sameeksha Sankpal
2025-05-19 15:19 ` Kees Cook
2025-05-28 1:08 ` [PATCH v2] selftests/seccomp: Improve error logging in get_proc_stat() Sameeksha Sankpal
2025-05-28 16:36 ` Kees Cook
2025-05-29 22:55 ` [PATCH v3] selftests/seccomp: Fix indentation and rebase error logging patch Sameeksha Sankpal
[not found] ` <CAGZaOhe0++vMANe1cAXXz=Pt1pf3ZX1vk3U7c0nGRnGGkt8e3A@mail.gmail.com>
[not found] ` <66a49c4b-2008-4059-97aa-59d53fb91c31@linuxfoundation.org>
2025-11-25 4:04 ` Sameeksha Sankpal
2025-11-25 17:25 ` Shuah Khan [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=588480bb-f498-400d-8241-6a317709b514@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=sameekshasankpal@gmail.com \
--cc=shuah@kernel.org \
--cc=wad@chromium.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