From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] alsa-utils: Version bump. 1.2.6 -> 1.2.8
Date: Tue, 22 Nov 2022 14:20:16 +0100 [thread overview]
Message-ID: <20221122132016.3159430-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20221118192545.1476812-2-christian.melki@t2data.com>
Thanks, applied as 243780d8357d443940f725a239fdf4fa7bb96df7.
Michael
[sent from post-receive hook]
On Tue, 22 Nov 2022 14:20:16 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Was lagging one release behind. Update utils.
> Some minor changes, nothing overly exciting.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20221118192545.1476812-2-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/alsa-utils.make b/rules/alsa-utils.make
> index a71744d7ea3b..1b10110bb9e3 100644
> --- a/rules/alsa-utils.make
> +++ b/rules/alsa-utils.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_ALSA_UTILS) += alsa-utils
> #
> # Paths and names
> #
> -ALSA_UTILS_VERSION := 1.2.6
> -ALSA_UTILS_MD5 := fc109b2fa4517caeae1697d936ca78ff
> +ALSA_UTILS_VERSION := 1.2.8
> +ALSA_UTILS_MD5 := 51175f5cd413daf7009a80684c65113d
> ALSA_UTILS := alsa-utils-$(ALSA_UTILS_VERSION)
> ALSA_UTILS_SUFFIX := tar.bz2
> ALSA_UTILS_URL := \
next prev parent reply other threads:[~2022-11-22 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 19:25 [ptxdist] [PATCH] alsa-lib: Version bump. 1.2.7.2 " Christian Melki
2022-11-18 19:25 ` [ptxdist] [PATCH] alsa-utils: Version bump. 1.2.6 " Christian Melki
2022-11-22 13:20 ` Michael Olbrich [this message]
2022-11-22 13:20 ` [ptxdist] [APPLIED] alsa-lib: Version bump. 1.2.7.2 " 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=20221122132016.3159430-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