All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/lvm2: enable device-mapper in Kernel config
Date: Thu, 9 May 2024 17:46:40 +0200	[thread overview]
Message-ID: <20240509174640.757b565d@windsurf> (raw)
In-Reply-To: <20240412222459.1630158-1-ju.o@free.fr>

On Sat, 13 Apr 2024 00:24:58 +0200
Julien Olivain <ju.o@free.fr> wrote:

> LVM2 has a hard dependency on the device-mapper presence in the Kernel.
> This commit enables those mandatory Kernel configuration by defining
> the _LINUX_CONFIG_FIXUPS macro. This will make sure the final system
> image will end up in a working configuration.
> 
> This was suggested by Arnout in [1].
> 
> [1] https://lists.buildroot.org/pipermail/buildroot/2024-April/688776.html
> 
> Suggested-by: Arnout Vandecappelle <arnout@mind.be>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
>  package/lvm2/lvm2.mk | 5 +++++
>  1 file changed, 5 insertions(+)

Both applied, thanks!

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

  parent reply	other threads:[~2024-05-09 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 22:24 [Buildroot] [PATCH 1/2] package/lvm2: enable device-mapper in Kernel config Julien Olivain
2024-04-12 22:24 ` [Buildroot] [PATCH 2/2] support/testing: lvm2: remove kernel config fragment Julien Olivain
2024-05-09 15:46 ` Thomas Petazzoni via buildroot [this message]
2024-06-03 15:17   ` [Buildroot] [PATCH 1/2] package/lvm2: enable device-mapper in Kernel config Peter Korsgaard

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=20240509174640.757b565d@windsurf \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.com \
    /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.