From: Markus Elfring <Markus.Elfring@web.de>
To: Yonggil Song <yonggil.song@samsung.com>,
linux-f2fs-devel@lists.sourceforge.net, Chao Yu <chao@kernel.org>,
Daejun Park <daejun7.park@samsung.com>,
Dongjin Kim <dongjin_.kim@samsung.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Siwoo Jung <siu.jung@samsung.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] libf2fs: Fix calculation of usable segments for single zoned
Date: Tue, 8 Oct 2024 15:16:37 +0200 [thread overview]
Message-ID: <4366efe2-89cc-45bf-9d51-04a2afd2783e@web.de> (raw)
In-Reply-To: <20241007052122epcms2p8a7a733c92a8da751ac64af8a29de0303@epcms2p8>
…
> This patch fixes the bug by …
* How do you think about to choose another imperative wording
for an improved change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12-rc2#n94
* Would you like to add any tags (like “Fixes” and “Cc”) accordingly?
Regards,
Markus
next prev parent reply other threads:[~2024-10-08 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241007052122epcms2p8a7a733c92a8da751ac64af8a29de0303@epcms2p8>
2024-10-07 5:21 ` Yonggil Song
2024-10-08 9:02 ` Chao Yu
2024-10-08 13:16 ` Markus Elfring [this message]
[not found] ` <CGME20241007052122epcms2p8a7a733c92a8da751ac64af8a29de0303@epcms2p2>
2024-10-10 2:15 ` Yonggil Song
2024-10-10 4:31 ` Yonggil Song
[not found] ` <CGME20241007052122epcms2p8a7a733c92a8da751ac64af8a29de0303@epcms2p7>
2024-10-10 4:59 ` [PATCH v2] libf2fs: Fix calculation of usable segments for single Yonggil Song
2024-10-11 15:34 ` Jaegeuk Kim
[not found] ` <CGME20241007052122epcms2p8a7a733c92a8da751ac64af8a29de0303@epcms2p3>
2024-10-14 1:43 ` Yonggil Song
2024-10-10 5:08 ` [RESEND][PATCH v2] libf2fs: Fix calculation of usable segments for single zoned device Yonggil Song
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=4366efe2-89cc-45bf-9d51-04a2afd2783e@web.de \
--to=markus.elfring@web.de \
--cc=chao@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=dongjin_.kim@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=siu.jung@samsung.com \
--cc=yonggil.song@samsung.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
all inboxes | Powered by JetHome®