From: Danny Milosavljevic <dannym@scratchpost.org>
To: raingloom <raingloom@riseup.net>
Cc: 41015@debbugs.gnu.org
Subject: [bug#41015] [PATCH] (incomplete) F2FS support
Date: Sat, 2 May 2020 11:02:45 +0200 [thread overview]
Message-ID: <20200502110245.45cc4b21@scratchpost.org> (raw)
In-Reply-To: <20200502024800.4b741809@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
Hi,
thanks!
I know exactly what you mean--I've had some "fun" preparing initrds too.
Pushed the first patch to guix master as commit 23b37c3d40d497cc6f07437ab26ab10e60fb6e09
and a variant of your fourth patch to guix master as commit 27efeef3068bfa21011ea509e21efcbe8c353b5f
so you should be able to at least boot.
Note:
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/tree/include/linux/f2fs_fs.h says volume name can have up to 512 chars.
Your comment says 16, but your code uses 512. I've fixed comment to say 512.
fsck progress so far: fsck.f2fs links to libuuid dynamically...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-05-02 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 0:48 [bug#41015] [PATCH] (incomplete) F2FS support raingloom
2020-05-02 9:02 ` Danny Milosavljevic [this message]
2020-05-02 9:40 ` Danny Milosavljevic
2020-05-02 9:56 ` Danny Milosavljevic
2020-05-03 21:05 ` bug#41015: " Danny Milosavljevic
2020-05-02 9:59 ` [bug#41015] " Danny Milosavljevic
2020-05-03 10:41 ` Danny Milosavljevic
2020-05-02 10:04 ` Danny Milosavljevic
2020-05-03 18:47 ` Danny Milosavljevic
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200502110245.45cc4b21@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=41015@debbugs.gnu.org \
--cc=raingloom@riseup.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).