From: Chao Yu <chao@kernel.org>
To: Tomas Mudrunka <mudrunka@spoje.net>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] F2FS support in genimage
Date: Mon, 28 Mar 2022 11:25:19 +0800 [thread overview]
Message-ID: <e8811d37-8987-cca5-78f5-9d17beff3a1d@kernel.org> (raw)
In-Reply-To: <7f4d6d15166e4df14a42fa7a3bc7e914@spoje.net>
On 2022/3/26 0:02, Tomas Mudrunka wrote:
> Dne 2022-03-21 07:03, Chao Yu napsal:
>> Hi Tomas,
>> Can sload.f2fs satisfy this requirement?
>> Thanks,
>
> BTW it worked, so we've already added F2FS support to genimage:
>
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpengutronix%2Fgenimage%2Fpull%2F185&data=04%7C01%7Cchao.yu%40oppo.com%7C4c4542946f1847d929e108da0e78ef11%7Cf1905eb1c35341c5951662b4a54b5ee6%7C0%7C0%7C637838210787573814%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Or%2Bt4bFIjSXQJFY9cpmo%2BxolyvMwsR3ymW%2B2BcVJeyk%3D&reserved=0
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpengutronix%2Fgenimage%2F&data=04%7C01%7Cchao.yu%40oppo.com%7C4c4542946f1847d929e108da0e78ef11%7Cf1905eb1c35341c5951662b4a54b5ee6%7C0%7C0%7C637838210787573814%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=suJsCc9%2BfDM66JUFC4GhPSORMBxkuYWCvX8Jw4dQuME%3D&reserved=0
>
> Someone might find that helpful
Thanks for the work. :)
Thanks,
>
> Cheers
>
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2022-03-28 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 12:55 [f2fs-dev] Populate f2fs with files during mkfs.f2fs Tomas Mudrunka
2022-03-21 6:03 ` Chao Yu
2022-03-21 7:59 ` Tomas Mudrunka
2022-03-25 16:02 ` [f2fs-dev] F2FS support in genimage Tomas Mudrunka
2022-03-28 3:25 ` Chao Yu [this message]
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=e8811d37-8987-cca5-78f5-9d17beff3a1d@kernel.org \
--to=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=mudrunka@spoje.net \
/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).