From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Hongbo Li <lihongbo22@huawei.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 0/9] f2fs: new mount API conversion
Date: Thu, 12 Sep 2024 09:11:51 +0800 [thread overview]
Message-ID: <cedd86de-4749-4880-93dd-373188bbfd47@kernel.org> (raw)
In-Reply-To: <adbbf133-08e3-4990-85a3-9dfa9d72c9fa@huawei.com>
On 2024/9/11 10:04, Hongbo Li wrote:
> Is the subject of the email required to be [f2fs-dev][PATCH]?
Hongbo,
"[f2fs-dev]" prefix is added by f2fs mailing list when it forwards
your patch to someone who subscribes the list, if you receive a patch
w/o f2fs-dev prefix, it is because you Sent/Cced patch to yourself,
and the list selected to not send you another email which has prefix
based on your mailing list option, IIUC.
So, it doesn't matter. :)
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-09-12 1:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 2:39 [f2fs-dev] [PATCH 0/9] f2fs: new mount API conversion Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 1/9] f2fs: Add fs parameter specifications for mount options Hongbo Li via Linux-f2fs-devel
2024-08-30 21:00 ` Eric Sandeen
2024-08-14 2:39 ` [f2fs-dev] [PATCH 2/9] f2fs: move the option parser into handle_mount_opt Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 3/9] f2fs: move option validation into a separate helper Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 4/9] f2fs: Allow sbi to be NULL in f2fs_printk Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 5/9] f2fs: Add f2fs_fs_context to record the mount options Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 6/9] f2fs: separate the options parsing and options checking Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 7/9] f2fs: introduce fs_context_operation structure Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 8/9] f2fs: switch to the new mount api Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 9/9] f2fs: remove unused structure and functions Hongbo Li via Linux-f2fs-devel
2024-08-27 11:47 ` [f2fs-dev] [PATCH 0/9] f2fs: new mount API conversion Hongbo Li via Linux-f2fs-devel
2024-08-30 17:07 ` Eric Sandeen
2024-08-31 1:45 ` Hongbo Li via Linux-f2fs-devel
2024-09-11 2:04 ` Hongbo Li via Linux-f2fs-devel
2024-09-12 1:11 ` Chao Yu via Linux-f2fs-devel [this message]
2024-09-12 1:49 ` Hongbo Li via Linux-f2fs-devel
2025-07-11 16:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
-- strict thread matches above, loose matches on Subject: below --
2024-08-12 9:12 Hongbo Li via Linux-f2fs-devel
2024-08-12 10:43 ` Hongbo Li via Linux-f2fs-devel
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=cedd86de-4749-4880-93dd-373188bbfd47@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=lihongbo22@huawei.com \
/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).