mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] mtd-utils: Version bump. 2.2.1 -> 2.3.0
Date: Fri, 21 Feb 2025 18:08:16 +0100	[thread overview]
Message-ID: <20250221170816.3902982-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250217171237.3729418-1-christian.melki@t2data.com>

Thanks, applied as d378503e6d337569f0990b1a17672bc60ffa8d00.

Michael

[sent from post-receive hook]

On Fri, 21 Feb 2025 18:08:16 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Perhaps the most interesting bit is the ubifs-fsck:er.
> https://lists.infradead.org/pipermail/linux-mtd/2025-February/108248.html
> 
> * Rearrange options, make zlib enabled as it is mandatory per .in.
> 
> * Forward patchset. Applies cleanly.
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20250217171237.3729418-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/patches/mtd-utils-2.2.1/0001-nandmarkbad-new-util-to-mark-blocks-as-bad.patch b/patches/mtd-utils-2.3.0/0001-nandmarkbad-new-util-to-mark-blocks-as-bad.patch
> similarity index 100%
> rename from patches/mtd-utils-2.2.1/0001-nandmarkbad-new-util-to-mark-blocks-as-bad.patch
> rename to patches/mtd-utils-2.3.0/0001-nandmarkbad-new-util-to-mark-blocks-as-bad.patch
> diff --git a/patches/mtd-utils-2.2.1/autogen.sh b/patches/mtd-utils-2.3.0/autogen.sh
> similarity index 100%
> rename from patches/mtd-utils-2.2.1/autogen.sh
> rename to patches/mtd-utils-2.3.0/autogen.sh
> diff --git a/patches/mtd-utils-2.2.1/series b/patches/mtd-utils-2.3.0/series
> similarity index 100%
> rename from patches/mtd-utils-2.2.1/series
> rename to patches/mtd-utils-2.3.0/series
> diff --git a/rules/mtd-utils.make b/rules/mtd-utils.make
> index def360ae3968..84989ace4d36 100644
> --- a/rules/mtd-utils.make
> +++ b/rules/mtd-utils.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_MTD_UTILS) += mtd-utils
>  #
>  # Paths and names
>  #
> -MTD_UTILS_VERSION	:= 2.2.1
> -MTD_UTILS_MD5		:= 08b97c0df7e70916a7b42460b5030fff
> +MTD_UTILS_VERSION	:= 2.3.0
> +MTD_UTILS_MD5		:= 06be1bd123cfea8575829e9b16e84f4b
>  MTD_UTILS		:= mtd-utils-$(MTD_UTILS_VERSION)
>  MTD_UTILS_SUFFIX	:= tar.bz2
>  MTD_UTILS_URL		:= https://infraroot.at/pub/mtd/$(MTD_UTILS).$(MTD_UTILS_SUFFIX)
> @@ -35,11 +35,13 @@ MTD_UTILS_CONF_OPT	:= \
>  	$(CROSS_AUTOCONF_USR) \
>  	--disable-unit-tests \
>  	$(GLOBAL_LARGE_FILE_OPTION) \
> -	--$(call ptx/wwo,PTXCONF_MTD_UTILS_TESTS)-tests \
>  	--$(call ptx/endis,PTXCONF_MTD_UTILS_UBIHEALTHD)-ubihealthd \
> +	--disable-asan \
> +	--$(call ptx/wwo,PTXCONF_MTD_UTILS_TESTS)-tests \
>  	--$(call ptx/wwo, PTXCONF_MTD_UTILS_LSMTD)-lsmtd \
>  	--$(call ptx/wwo, PTXCONF_MTD_UTILS_JFFS)-jffs \
>  	--$(call ptx/wwo, PTXCONF_MTD_UTILS_UBIFS)-ubifs \
> +	--with-zlib \
>  	--without-xattr \
>  	--$(call ptx/wwo, PTXCONF_MTD_UTILS_USE_LIBLZO)-lzo \
>  	--without-zstd \



      parent reply	other threads:[~2025-02-21 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 17:12 [ptxdist] [PATCH] " Christian Melki
2025-02-18  7:39 ` Michael Olbrich
2025-02-21 17:08 ` 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=20250221170816.3902982-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.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