From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Livius <egyszeregy@freemail.hu>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] wic - Plans for support F2FS file system type for the partition?
Date: Sat, 21 May 2022 22:02:12 +0200 [thread overview]
Message-ID: <CANNYZj-Fv9gAeKdZgQ5ev393NYYKdZRN7TTPdf4A-aSzELJ9iw@mail.gmail.com> (raw)
In-Reply-To: <L6Uf.1653156831053364784.vSAI@lists.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
If you can add support for it and send patches, that would be most welcome.
We don’t have a magic team of developers that take feature requests and
implement them.
Alex
On Sat 21. May 2022 at 20.13, Livius <egyszeregy@freemail.hu> wrote:
> In OpenEmbedded Kickstart Reference manual
> <https://docs.yoctoproject.org/ref-manual/kickstart.html> there are no
> any support for F2FS filesystem <https://en.wikipedia.org/wiki/F2FS> in
> *--fstype* options. Could you support it and plan to implement? It seems
> to me this file system type can be the best for eMMC and SD cards and it is
> fully supported in Linux for rootfs, nowadays.
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#165964):
> https://lists.openembedded.org/g/openembedded-core/message/165964
> Mute This Topic: https://lists.openembedded.org/mt/91256476/1686489
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
[-- Attachment #2: Type: text/html, Size: 2027 bytes --]
prev parent reply other threads:[~2022-05-21 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 18:13 wic - Plans for support F2FS file system type for the partition? Livius
2022-05-21 20:02 ` Alexander Kanavin [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=CANNYZj-Fv9gAeKdZgQ5ev393NYYKdZRN7TTPdf4A-aSzELJ9iw@mail.gmail.com \
--to=alex.kanavin@gmail.com \
--cc=egyszeregy@freemail.hu \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.