From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Tianyi Chen <diannaaav@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Shuah Khan <shuah@kernel.org>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, Joel Savitz <jsavitz@redhat.com>
Subject: Re: [PATCH RESEND v3 1/2] selftests/mm: Reject invalid test selections before running tests
Date: Thu, 10 Sep 2026 12:30:30 +0200 [thread overview]
Message-ID: <5cf58cd3-4b36-4f8b-82c0-c678b0226c60@kernel.org> (raw)
In-Reply-To: <CACGbirSm=AZtAVwJAZRZt0JAGGUGVOCUQVqu-EcEiiGC-=+vJA@mail.gmail.com>
On 9/10/26 12:25, Tianyi Chen wrote:
> Hi David,
>
>> How did you send out the previous revision? Through b4 or git send-mail?
>
> The v3 sent from hi@tychen.cc on September 8 used git send-email via
> SpaceMail SMTP. The inline Gmail resend on September 9 used Codex's
> Gmail connector. The patches were generated with git format-patch.
>
> The Gmail Sent copy was intact, but the copy received outside Gmail
> had wrapped diff headers and altered whitespace. The attachments were
> a workaround for that sending path. I agree they are inconvenient for
> review.
Yeah, you have to find a way to fix that. I used to send patches through gmail's
smtp and it never resulted in something like this.
--
Cheers,
David
next prev parent reply other threads:[~2026-09-10 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 15:23 [PATCH RESEND v3 0/2] selftests/mm: Validate selections and scope memfd_secret setup Tianyi Chen
2026-09-09 15:23 ` [PATCH RESEND v3 1/2] selftests/mm: Reject invalid test selections before running tests Tianyi Chen
2026-09-09 15:33 ` David Hildenbrand (Arm)
2026-09-10 10:25 ` Tianyi Chen
2026-09-10 10:30 ` David Hildenbrand (Arm) [this message]
2026-09-09 15:23 ` [PATCH RESEND v3 2/2] selftests/mm: Only prepare ptrace_scope when memfd_secret is selected Tianyi Chen
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=5cf58cd3-4b36-4f8b-82c0-c678b0226c60@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=diannaaav@gmail.com \
--cc=jsavitz@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.