From: Markus Elfring <Markus.Elfring@web.de>
To: Sayali Lokhande <sayalil@codeaurora.org>,
linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: Avoid double lock for cp_rwsem
Date: Thu, 23 Apr 2020 15:07:20 +0200 [thread overview]
Message-ID: <8f311cd7-bf6d-21a4-c085-6b2feec39717@web.de> (raw)
> Call stack :
> f2fs_write_checkpoint()
> -> block_operations(sbi)
…
Will another imperative wording become helpful besides the provided information
for this change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=c578ddb39e565139897124e74e5a43e56538cb33#n151
How do you think about to add the tag “Fixes” because of adjustments
for the data synchronisation?
Regards,
Markus
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2020-04-23 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 13:07 Markus Elfring [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-23 10:13 [f2fs-dev] [PATCH] f2fs: Avoid double lock for cp_rwsem Sayali Lokhande
2020-04-23 13:13 ` Chao Yu
2020-04-23 20:19 ` Jaegeuk Kim
2020-04-24 0:16 ` Jaegeuk Kim
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=8f311cd7-bf6d-21a4-c085-6b2feec39717@web.de \
--to=markus.elfring@web.de \
--cc=jaegeuk@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sayalil@codeaurora.org \
--cc=yuchao0@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).