From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Leonard Göhrs" <l.goehrs@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] util-linux: add support for enabling the findmnt command
Date: Wed, 14 May 2025 08:07:35 +0200 [thread overview]
Message-ID: <20250514060735.498851-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250428054246.1693430-1-l.goehrs@pengutronix.de>
Thanks, applied as f64a42bc82ec735d79cb06e0d21758484857a125.
Michael
[sent from post-receive hook]
On Wed, 14 May 2025 08:07:35 +0200, Leonard Göhrs <l.goehrs@pengutronix.de> wrote:
> Signed-off-by: Leonard Göhrs <l.goehrs@pengutronix.de>
> Message-Id: <20250428054246.1693430-1-l.goehrs@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/util-linux.in b/rules/util-linux.in
> index 3effecd72a9b..1118c7033f98 100644
> --- a/rules/util-linux.in
> +++ b/rules/util-linux.in
> @@ -94,6 +94,12 @@ config UTIL_LINUX_FDISK
> comment "BusyBox' fdisk is selected!"
> depends on BUSYBOX_FDISK
>
> +config UTIL_LINUX_FINDMNT
> + bool
> + prompt "findmnt"
> + help
> + findmnt - Find a mounted device from its mountpoint and vise versa
> +
> config UTIL_LINUX_FSCK
> bool
> prompt "fsck"
> diff --git a/rules/util-linux.make b/rules/util-linux.make
> index c1152257dd6f..cebaf9c45db6 100644
> --- a/rules/util-linux.make
> +++ b/rules/util-linux.make
> @@ -78,7 +78,7 @@ UTIL_LINUX_CONF_OPT := \
> -Dbuild-fdformat=disabled \
> -Dbuild-fdisks=$(call ptx/endis, PTXCONF_UTIL_LINUX_FDISKS)d \
> -Dbuild-findfs=$(call ptx/endis, PTXCONF_UTIL_LINUX_FINDFS)d \
> - -Dbuild-findmnt=disabled \
> + -Dbuild-findmnt=$(call ptx/endis, PTXCONF_UTIL_LINUX_FINDMNT)d \
> -Dbuild-flock=$(call ptx/endis, PTXCONF_UTIL_LINUX_FLOCK)d \
> -Dbuild-fsck=$(call ptx/endis, PTXCONF_UTIL_LINUX_FSCK)d \
> -Dbuild-fsfreeze=$(call ptx/endis, PTXCONF_UTIL_LINUX_FSFREEZE)d \
> @@ -233,6 +233,7 @@ UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_SULOGIN) += sbin/sulogin
> # misc-utils
> UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_BLKID) += sbin/blkid
> UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_FINDFS) += sbin/findfs
> +UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_FINDMNT) += bin/findmnt
> UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_GETOPT) += bin/getopt
> UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_LSBLK) += bin/lsblk
> UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_MCOOKIE) += bin/mcookie
prev parent reply other threads:[~2025-05-14 6:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 5:42 [ptxdist] [PATCH v2] " Leonard Göhrs
2025-05-14 6:07 ` Michael Olbrich [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=20250514060735.498851-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=l.goehrs@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox