From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Jonas Rebmann <jre@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] util-linux: make blkdiscard selectable
Date: Mon, 27 Jan 2025 09:35:15 +0100 [thread overview]
Message-ID: <20250127083515.363258-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250123-blkdiscard-v1-1-a8a4541186d5@pengutronix.de>
Thanks, applied as fc9e466c9b74d524d3c9a62eaaa5e7f80a4e3cad.
Michael
[sent from post-receive hook]
On Mon, 27 Jan 2025 09:35:15 +0100, Jonas Rebmann <jre@pengutronix.de> wrote:
> Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
> Message-Id: <20250123-blkdiscard-v1-1-a8a4541186d5@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/util-linux.in b/rules/util-linux.in
> index 8bf035f3901e..58bd21100a9e 100644
> --- a/rules/util-linux.in
> +++ b/rules/util-linux.in
> @@ -290,6 +290,18 @@ comment "BusyBox' taskset is selected!"
>
> comment "sys-utils"
>
> +config UTIL_LINUX_BLKDISCARD
> + bool
> + depends on !BUSYBOX_BLKDISCARD || ALLYES
> + prompt "blkdiscard"
> + help
> + blkdiscard is used to discard device sectors. This is useful for
> + solid-state drivers (SSDs) and thinly-provisioned storage. Unlike
> + fstrim, this command is used directly on the block device.
> +
> +comment "BusyBox' blkdiscard is selected!"
> + depends on BUSYBOX_BLKDISCARD
> +
> config UTIL_LINUX_CHMEM
> bool
> prompt "chmem"
> diff --git a/rules/util-linux.make b/rules/util-linux.make
> index 579c165e6edb..c98200a52258 100644
> --- a/rules/util-linux.make
> +++ b/rules/util-linux.make
> @@ -54,7 +54,7 @@ UTIL_LINUX_CONF_OPT := \
> -Dbuild-agetty=$(call ptx/endis, PTXCONF_UTIL_LINUX_AGETTY)d \
> -Dbuild-bash-completion=disabled \
> -Dbuild-bfs=disabled \
> - -Dbuild-blkdiscard=disabled \
> + -Dbuild-blkdiscard=$(call ptx/endis, PTXCONF_UTIL_LINUX_BLKDISCARD)d \
> -Dbuild-blkpr=disabled \
> -Dbuild-blkzone=disabled \
> -Dbuild-blockdev=disabled \
> @@ -223,6 +223,7 @@ UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_CHRT) += bin/chrt
> UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_IONICE) += bin/ionice
> UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_TASKSET) += bin/taskset
> # sys-utils
> +UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_BLKDISCARD) += sbin/blkdiscard
> UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_CHMEM) += bin/chmem
> UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_DMESG) += bin/dmesg
> UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_FLOCK) += bin/flock
prev parent reply other threads:[~2025-01-27 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 20:59 [ptxdist] [PATCH] " Jonas Rebmann
2025-01-27 8:35 ` 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=20250127083515.363258-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=jre@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