From: Justin Bronder <jsbronder@cold-front.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: kbuild: use lz4 instead of lz4c
Date: Tue, 26 Nov 2024 09:45:21 -0500 [thread overview]
Message-ID: <Z0XfAbL5LbZjzISw@ravine.members.linode.com> (raw)
In-Reply-To: <CAK7LNARCB0Ce=gYjEZE1uSP0_Oyht91zxTQ1RZrMiChe3vgy+g@mail.gmail.com>
On 26/11/24 13:26 +0900, Masahiro Yamada wrote:
> On Tue, Nov 26, 2024 at 2:18 AM Justin Bronder <jsbronder@cold-front.org> wrote:
> >
> > lz4c has been considered deprecated by upstream since at least 2018 [1]
> > and has been disabled by default recently [2]. openSUSE Tumbleweed is
> > no longer packaging the deprecated version and others will likely
> > follow.
> >
> > Going back as far as Ubuntu 16.04/Fedora 25, both lz4 and lz4c are
> > installed as part of the same package and both accept -9 to enable high
> > compression so switching should be safe.
> >
> > 1. https://github.com/lz4/lz4/pull/553
> > 2. https://github.com/lz4/lz4/pull/1479
> >
> > Signed-off-by: Justin Bronder <jsbronder@cold-front.org>
>
>
> I already applied a similar patch.
>
> https://lore.kernel.org/linux-kbuild/CAK7LNAS0VzqcKDz_1ds5qJcASqxVizE3kkdRk1Yiidch9KMxEQ@mail.gmail.com/T/#t
Ah, apologies for not noticing that. That patch definitely covers what I was
trying to achieve, so this one can be can be dropped.
Thanks!
--
Justin Bronder
prev parent reply other threads:[~2024-11-26 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 17:18 [PATCH] kbuild: use lz4 instead of lz4c Justin Bronder
2024-11-26 4:26 ` Masahiro Yamada
2024-11-26 14:45 ` Justin Bronder [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=Z0XfAbL5LbZjzISw@ravine.members.linode.com \
--to=jsbronder@cold-front.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
/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