From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Li Zetao <lizetao1@huawei.com>, jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 1/8] f2fs: convert f2fs_write_begin() to use folio
Date: Wed, 21 Aug 2024 15:31:31 +0800 [thread overview]
Message-ID: <dfcfb276-1502-45da-b65d-e7ce5297d6ae@kernel.org> (raw)
In-Reply-To: <a16d5083-5e24-43e1-b245-12152cac5947@kernel.org>
On 2024/8/20 14:58, Chao Yu wrote:
> On 2024/8/20 12:38, Li Zetao wrote:
>>> I want to apply your patch set for testing, but there is a conflict on
>> the master branch of linux-next. Maybe it depends on a certain pre-patch. Please let me know, thank you.
>>
>> Applying: f2fs: convert f2fs_write_begin() to use folio
>> error: patch failed: fs/f2fs/data.c:3566
>> error: fs/f2fs/data.c: patch does not apply
>> Patch failed at 0001 f2fs: convert f2fs_write_begin() to use folio
>
> We should apply this patchset on top of dev-test branch?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/log/?h=dev-test
Oh, I missed one patch...
Can you please check
https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/log/?h=folio
Thanks,
>
> Thanks,
>
>>
>> Thanks,
>> Li Zetao.
>
>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
_______________________________________________
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-08-21 7:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 3:46 [f2fs-dev] [PATCH v2 1/8] f2fs: convert f2fs_write_begin() to use folio Chao Yu
2024-08-20 3:46 ` [f2fs-dev] [PATCH v2 2/8] f2fs: convert f2fs_write_end() " Chao Yu
2024-08-20 3:46 ` [f2fs-dev] [PATCH v2 3/8] f2fs: convert f2fs_set_compressed_page() " Chao Yu
2024-08-20 3:46 ` [f2fs-dev] [PATCH v2 4/8] f2fs: convert f2fs_do_write_data_page() " Chao Yu
2024-08-20 3:46 ` [f2fs-dev] [PATCH v2 5/8] f2fs: convert f2fs_write_data_page() " Chao Yu
2024-08-20 3:46 ` [f2fs-dev] [PATCH v2 6/8] f2fs: convert __write_node_page() " Chao Yu
2024-08-20 3:46 ` [f2fs-dev] [PATCH v2 7/8] f2fs: convert read_node_page() " Chao Yu
2024-08-20 3:46 ` [f2fs-dev] [PATCH v2 8/8] f2fs: get rid of page->index Chao Yu
2024-08-20 4:38 ` [f2fs-dev] [PATCH v2 1/8] f2fs: convert f2fs_write_begin() to use folio Li Zetao via Linux-f2fs-devel
2024-08-20 6:58 ` Chao Yu
2024-08-21 7:31 ` Chao Yu via Linux-f2fs-devel [this message]
2024-08-30 20:51 ` patchwork-bot+f2fs--- 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=dfcfb276-1502-45da-b65d-e7ce5297d6ae@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizetao1@huawei.com \
--cc=willy@infradead.org \
/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).