From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v4] f2fs: compress: support chksum
Date: Wed, 9 Dec 2020 00:23:15 -0800 [thread overview]
Message-ID: <X9CJc7xas7OqTZv2@google.com> (raw)
In-Reply-To: <0d4a20ec-f6e4-ff24-8733-94cc3762195d@huawei.com>
On 12/09, Chao Yu wrote:
> On 2020/12/9 12:28, Chao Yu wrote:
> > On 2020/12/9 11:54, Jaegeuk Kim wrote:
> > > Ah, could you please write another patch to adjust the new changes?
> >
> > No problem, will drop "f2fs: compress:support chksum" based on your dev branch, and
> > apply all compress related patches on top of dev branch.
>
> Jaegeuk, could you please
> - drop "f2fs: compress:support chksum",
What I mean is keeping the old version in dev branch as is, since it gives
another conflicts when dropping it. That can add another bug at this point.
Can I get a separate patch to fix any issues in that original patch?
> - manually fix conflict when applying "f2fs: add compress_mode mount option"
> - and then apply last my resent patches.
>
> 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:[~2020-12-09 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 3:14 [f2fs-dev] [PATCH v4] f2fs: compress: support chksum Chao Yu
2020-12-09 1:37 ` Chao Yu
2020-12-09 2:49 ` Jaegeuk Kim
2020-12-09 3:05 ` Chao Yu
2020-12-09 3:54 ` Jaegeuk Kim
2020-12-09 4:28 ` Chao Yu
2020-12-09 6:29 ` Chao Yu
2020-12-09 8:23 ` Jaegeuk Kim [this message]
2020-12-09 8:31 ` Chao Yu
2020-12-09 8:42 ` Chao Yu
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=X9CJc7xas7OqTZv2@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).