mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] util-linux: add option for building blkdiscard
Date: Mon, 27 Jan 2025 11:46:16 +0100	[thread overview]
Message-ID: <Z5dj-MrvmgQivnI7@pengutronix.de> (raw)
In-Reply-To: <20250127083516.363301-1-m.olbrich@pengutronix.de>

On Mon, Jan 27, 2025 at 09:35:16AM +0100, Michael Olbrich wrote:
> Thanks, applied as 9e0602b0e355efaf23b6306c813aa54630d101da.

And as Jonas noted, I've now applied two patches for the same thing... I'll
revert this one.

Michael

> [sent from post-receive hook]
> 
> On Mon, 27 Jan 2025 09:35:16 +0100, Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
> > We currently only have an option for BusyBox blkdiscard, but that one
> > lacks some options like -z for zeroing the block device.
> > 
> > This can be important as regular discard on an eMMC isn't guaranteed
> > to clear data.
> > 
> > Add a util-linux blkdiscard option to address this.
> > 
> > Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> > Message-Id: <20250123205453.2841392-1-a.fatoum@pengutronix.de>
> > Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> > 
> > diff --git a/rules/util-linux.in b/rules/util-linux.in
> > index 58bd21100a9e..d883fb402ca2 100644
> > --- a/rules/util-linux.in
> > +++ b/rules/util-linux.in
> > @@ -62,6 +62,16 @@ config UTIL_LINUX_ADDPART
> >  	help
> >  	  The addpart utility.
> >  
> > +config UTIL_LINUX_BLKDISCARD
> > +	bool
> > +	depends on !BUSYBOX_BLKDISCARD || ALLYES
> > +	prompt "blkdiscard"
> > +	help
> > +	  blkdiscard is used to discard device sectors.
> > +
> > +comment "BusyBox' blkdiscard is selected!"
> > +	depends on BUSYBOX_BLKDISCARD
> > +
> >  config UTIL_LINUX_CFDISK
> >  	bool
> >  	select UTIL_LINUX_FDISKS
> > diff --git a/rules/util-linux.make b/rules/util-linux.make
> > index c98200a52258..143c7bcb78aa 100644
> > --- a/rules/util-linux.make
> > +++ b/rules/util-linux.make
> > @@ -197,6 +197,7 @@ UTIL_LINUX_LIB-$(PTXCONF_UTIL_LINUX_LIBFDISK)		+= fdisk
> >  
> >  # disk-utils
> >  UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_ADDPART)		+= sbin/addpart
> > +UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_BLKDISCARD)		+= sbin/blkdiscard
> >  UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_CFDISK)		+= sbin/cfdisk
> >  UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_DELPART)		+= sbin/delpart
> >  UTIL_LINUX_BIN-$(PTXCONF_UTIL_LINUX_RESIZEPART)		+= sbin/resizepart
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2025-01-27 10:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 20:54 [ptxdist] [PATCH] " Ahmad Fatoum
2025-01-23 21:55 ` Christian Melki
2025-01-23 22:02   ` Ahmad Fatoum
2025-01-27  8:35 ` [ptxdist] [APPLIED] " Michael Olbrich
2025-01-27 10:46   ` 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=Z5dj-MrvmgQivnI7@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=a.fatoum@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