From: Julian Sun <sunjunchao2870@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
viro@zeniv.linux.org.uk, jack@suse.cz, stable@vger.kernel.org,
syzbot+296b1c84b9cbf306e5a0@syzkaller.appspotmail.com,
Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH 2/3] vfs: Fix implicit conversion problem when testing overflow case
Date: Thu, 26 Sep 2024 17:06:34 +0800 [thread overview]
Message-ID: <CAHB1Naj2gZ7CuHeQXMNtYfRaMarRP85SEXq7YfWB0NQu_hzB+g@mail.gmail.com> (raw)
In-Reply-To: <20240925-anflug-flossen-071b110c324b@brauner>
Christian Brauner <brauner@kernel.org> 于2024年9月25日周三 16:37写道：
>
> Unrelated to the semantics but why do you use 2/3 numbering for a single
> patch? This is really confusing.
Sorry for the inconvenience. I used git send-email --to xxx --cc xxx
./*.patch to send my patch series. My intention was to send the three
patches together as a thread, but it clearly didn’t work out... I’ve
tried Google and ChatGPT but couldn’t find any information on how to
send a patch series as a single thread... The other two patches are
here[1][2], but they still need to be refined
[1]: https://lore.kernel.org/linux-fsdevel/20240920122621.215397-1-sunjunchao2870@gmail.com/
[2]:https://lore.kernel.org/linux-fsdevel/20240920123022.215863-1-sunjunchao2870@gmail.com/
Thanks,
--
Julian Sun <sunjunchao2870@gmail.com>
prev parent reply other threads:[~2024-09-26 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 12:28 [PATCH 2/3] vfs: Fix implicit conversion problem when testing overflow case Julian Sun
2024-09-20 14:17 ` Christoph Hellwig
2024-09-20 14:38 ` Darrick J. Wong
2024-09-25 8:36 ` Christian Brauner
2025-01-06 8:35 ` Julian Sun
2024-09-25 8:37 ` Christian Brauner
2024-09-26 9:06 ` Julian Sun [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=CAHB1Naj2gZ7CuHeQXMNtYfRaMarRP85SEXq7YfWB0NQu_hzB+g@mail.gmail.com \
--to=sunjunchao2870@gmail.com \
--cc=brauner@kernel.org \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+296b1c84b9cbf306e5a0@syzkaller.appspotmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).