All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Thierry Bultel <thierry.bultel@linatsea.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 3/3] fs/cpio: new option to use dracut tool
Date: Sun, 19 Dec 2021 11:13:36 +0100	[thread overview]
Message-ID: <20211219111336.49cd5d7a@windsurf> (raw)
In-Reply-To: <20211219073119.1087539-3-thierry.bultel@linatsea.fr>

Hello Thierry,

On Sun, 19 Dec 2021 08:31:19 +0100
Thierry Bultel <thierry.bultel@linatsea.fr> wrote:

> Adds an option to invoke the dracut host tool, providing
> a configuration file, instead of having a full cpio archive
> of the whole target directory.
> 
> Signed-off-by: Thierry Bultel <thierry.bultel@linatsea.fr>
> Changes v1 -> v2 (suggested by Arnoult and Yann)
>   - was a new fs type, now an option of cpio
>   - deals with the case of a build with no kernel
>   - gets the kernel name in a smarter way
>   - checks for the name of dracut configuration file
> 
> Signed-off-by: Thierry Bultel <thierry.bultel@linatsea.fr>

Thanks for working on this! What would be nice is to add a test case in
support/testing/ for this. We already have lots of tests for various
filesystem types in support/testing/tests/fs.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-12-19 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-19  7:31 [Buildroot] [PATCH v2 1/3] package/cross-ldd: new package Thierry Bultel
2021-12-19  7:31 ` [Buildroot] [PATCH v2 2/3] package/dracut: new host package Thierry Bultel
2021-12-19  7:31 ` [Buildroot] [PATCH v2 3/3] fs/cpio: new option to use dracut tool Thierry Bultel
2021-12-19 10:13   ` Thomas Petazzoni [this message]
2021-12-23 11:20     ` Thierry Bultel

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=20211219111336.49cd5d7a@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=thierry.bultel@linatsea.fr \
    /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.