From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Alexander Egorenkov <egorenar-dev@posteo.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/makedumpfile: add zstd optional dependency
Date: Mon, 15 Aug 2022 12:01:39 +0200 [thread overview]
Message-ID: <20220815120139.027f1c2b@windsurf> (raw)
In-Reply-To: <20220815094934.296837-1-fontaine.fabrice@gmail.com>
On Mon, 15 Aug 2022 11:49:34 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> zstd is an optional dependency since bump to version 1.7.0 in commit
> bbc52f3ff382e4c50baea2e1876a3f6ebf77a851 and
> https://github.com/makedumpfile/makedumpfile/commit/afd0a6db2a0543217f8e46955a1b44b71f7e7ef3
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/makedumpfile/makedumpfile.mk | 5 +++++
> 1 file changed, 5 insertions(+)
We sometimes apply optional dependency handling patches to master, when
they have a "disable" logic that potentially avoids spurious detection.
But that's not the case here, so I have applied this patch to next. Let
me know if you disagree.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-08-15 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 9:49 [Buildroot] [PATCH 1/1] package/makedumpfile: add zstd optional dependency Fabrice Fontaine
2022-08-15 10:01 ` Thomas Petazzoni via buildroot [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=20220815120139.027f1c2b@windsurf \
--to=buildroot@buildroot.org \
--cc=egorenar-dev@posteo.net \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.