From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next 1/1] package/libdeflate: bump version to 1.18
Date: Sat, 29 Jul 2023 23:35:02 +0200 [thread overview]
Message-ID: <20230729233502.5a5948cf@windsurf> (raw)
In-Reply-To: <20230607171834.595904-1-bernd.kuhls@t-online.de>
On Wed, 7 Jun 2023 19:18:34 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Removed patches included in upstream release.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> ...-target-when-required-due-to-gcc-bug.patch | 90 -------------------
> ...or-due-to-PMULL-enabled-without-NEON.patch | 35 --------
> package/libdeflate/libdeflate.hash | 2 +-
> package/libdeflate/libdeflate.mk | 2 +-
> 4 files changed, 2 insertions(+), 127 deletions(-)
> delete mode 100644 package/libdeflate/0001-lib-arm-crc32-use-crypto-target-when-required-due-to-gcc-bug.patch
> delete mode 100644 package/libdeflate/0002-lib-arm-cpu_features-fix-build-error-due-to-PMULL-enabled-without-NEON.patch
You had forgotten to update .checkpackageignore after the removal of
the two patches that did not have an upstream tag, so I did that when
applying. 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:[~2023-07-29 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 17:18 [Buildroot] [PATCH/next 1/1] package/libdeflate: bump version to 1.18 Bernd Kuhls
2023-07-29 21:35 ` 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=20230729233502.5a5948cf@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd.kuhls@t-online.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox