mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Hubert Feurstein <h.feurstein@gmail.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 02/10] util-linux-ng: add fstrim option
Date: Fri,  6 Mar 2015 11:25:52 +0100	[thread overview]
Message-ID: <1425637560-23901-2-git-send-email-h.feurstein@gmail.com> (raw)
In-Reply-To: <1425637560-23901-1-git-send-email-h.feurstein@gmail.com>

Signed-off-by: Hubert Feurstein <h.feurstein@gmail.com>
---
 rules/util-linux-ng.in   | 12 ++++++++++++
 rules/util-linux-ng.make |  3 +++
 2 files changed, 15 insertions(+)

diff --git a/rules/util-linux-ng.in b/rules/util-linux-ng.in
index a5f51a6..50dfbf6 100644
--- a/rules/util-linux-ng.in
+++ b/rules/util-linux-ng.in
@@ -200,6 +200,18 @@ config UTIL_LINUX_NG_FSCK
 comment "BusyBox' fsck is selected!"
 	depends on BUSYBOX_FSCK
 
+config UTIL_LINUX_NG_FSTRIM
+	bool
+	prompt "fstrim"
+	depends on !BUSYBOX_FSTRIM || ALLYES
+	help
+	  fstrim is used on a mounted filesystem to discard (or "trim")
+	  blocks which are not in use by the filesystem. This is useful
+	  for solid-state drives (SSDs) and thinly-provisioned storage.
+
+comment "BusyBox' fstrim is selected!"
+	depends on BUSYBOX_FSTRIM
+
 config UTIL_LINUX_NG_IPCS
 	bool
 	prompt "ipcs"
diff --git a/rules/util-linux-ng.make b/rules/util-linux-ng.make
index fc28c66..acd3b78 100644
--- a/rules/util-linux-ng.make
+++ b/rules/util-linux-ng.make
@@ -205,6 +205,9 @@ endif
 ifdef PTXCONF_UTIL_LINUX_NG_FSCK
 	@$(call install_copy, util-linux-ng, 0, 0, 0755, -, /sbin/fsck)
 endif
+ifdef PTXCONF_UTIL_LINUX_NG_FSTRIM
+	@$(call install_copy, util-linux-ng, 0, 0, 0755, -, /sbin/fstrim)
+endif
 ifdef PTXCONF_UTIL_LINUX_NG_IPCS
 	@$(call install_copy, util-linux-ng, 0, 0, 0755, -, /usr/bin/ipcs)
 endif
-- 
2.3.0


-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-03-06 10:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 10:25 [ptxdist] [PATCH 01/10] chrony: version bump 1.29 -> 1.31 Hubert Feurstein
2015-03-06 10:25 ` Hubert Feurstein [this message]
2015-03-26  8:48   ` [ptxdist] [PATCH 02/10] util-linux-ng: add fstrim option Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 03/10] util-linux-ng: add dmesg option Hubert Feurstein
2015-03-26  8:49   ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 04/10] ethtool: version bump 3.0 -> 3.18 Hubert Feurstein
2015-03-26  8:51   ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 05/10] ethtool: add license information Hubert Feurstein
2015-03-26  8:51   ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 06/10] libksba: version bump 1.0.7 -> 1.3.2 Hubert Feurstein
2015-03-26  8:51   ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 07/10] libksba: add license information Hubert Feurstein
2015-03-26  8:52   ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 08/10] libassuan: version bump 2.0.0 -> 2.2.0 Hubert Feurstein
2015-03-26  8:53   ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 09/10] libassuan: add license information Hubert Feurstein
2015-03-26  8:53   ` Michael Olbrich
2015-03-06 10:26 ` [ptxdist] [PATCH 10/10] libgcrypt: version bump 1.5.3 -> 1.6.3 Hubert Feurstein
2015-03-21 17:17   ` Michael Olbrich
2015-03-26  8:50 ` [ptxdist] [PATCH 01/10] chrony: version bump 1.29 -> 1.31 Michael Olbrich

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=1425637560-23901-2-git-send-email-h.feurstein@gmail.com \
    --to=h.feurstein@gmail.com \
    --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