From: Tomas Mudrunka <mudrunka@spoje.net>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] F2FS support in genimage
Date: Fri, 25 Mar 2022 17:02:41 +0100 [thread overview]
Message-ID: <7f4d6d15166e4df14a42fa7a3bc7e914@spoje.net> (raw)
In-Reply-To: <b491875c-c6a8-1243-35cf-649be3250b5d@kernel.org>
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://github.com/pengutronix/genimage/pull/185
https://github.com/pengutronix/genimage/
Someone might find that helpful
Cheers
--
S pozdravem
Best regards
Tomáš Mudruňka
_______________________________________________
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:[~2022-03-25 16:03 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 ` Tomas Mudrunka [this message]
2022-03-28 3:25 ` [f2fs-dev] F2FS support in genimage 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=7f4d6d15166e4df14a42fa7a3bc7e914@spoje.net \
--to=mudrunka@spoje.net \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.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).