From: "Ludovic Courtès" <ludo@gnu.org>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 38462-done@debbugs.gnu.org, 38462@debbugs.gnu.org
Subject: [bug#38462] [PATCH] linux-boot: Don't ignore flags when mounting root file system.
Date: Tue, 10 Dec 2019 20:49:47 +0100 [thread overview]
Message-ID: <87fthsklk4.fsf@gnu.org> (raw)
In-Reply-To: <87k174kncu.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 10 Dec 2019 20:10:57 +0100")
Ludovic Courtès <ludo@gnu.org> skribis:
> Guillaume Le Vaillant <glv@posteo.net> skribis:
>
>> Ludovic Courtès skribis:
>>
>>> Guillaume Le Vaillant <glv@posteo.net> skribis:
>>>
>>>> * gnu/build/linux-boot.scm (mount-root-file-system): Add the 'flags' keyword
>>>> argument and use it when mounting the root file system.
>>>> (boot-system): Pass the root file system flags to 'mount-root-file-system'.
>>>
>>> This was pushed as 900ef20b1da66ad71145082c883dc12f31fafa54, closing!
>>>
>>> Ludo’.
>>
>> These are in fact two similar but different patches. Patch
>> 900ef20b1da66ad71145082c883dc12f31fafa54 added support for the 'options'
>> field of a file-system definition, whereas this patch adds support for
>> the 'flags' field.
>
> Oops, my bad. Applied, thanks!
Actually no: “make check-system TESTS=basic” fails after that.
Could you take a look?
Thanks in advance,
Ludo’.
next prev parent reply other threads:[~2019-12-10 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 20:57 [bug#38462] [PATCH] linux-boot: Don't ignore flags when mounting root file system Guillaume Le Vaillant
2019-12-09 14:53 ` bug#38462: " Ludovic Courtès
2019-12-09 15:22 ` [bug#38462] " Guillaume Le Vaillant
2019-12-10 19:10 ` Ludovic Courtès
2019-12-10 19:49 ` Ludovic Courtès [this message]
2019-12-10 22:37 ` [bug#38462] [PATCH v2] " Guillaume Le Vaillant
2019-12-12 16:55 ` Ludovic Courtès
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=87fthsklk4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38462-done@debbugs.gnu.org \
--cc=38462@debbugs.gnu.org \
--cc=glv@posteo.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).