From: Gao Xiang via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: linux-erofs@lists.ozlabs.org
Subject: [PATCH] erofs-utils: README: update known-issue status of lz4hc
Date: Mon, 12 Oct 2020 15:34:46 +0800 [thread overview]
Message-ID: <20201012073446.18103-1-hsiangkao@aol.com> (raw)
In-Reply-To: 20201012073446.18103-1-hsiangkao.ref@aol.com
Known issue of LZ4_compress_HC_destSize() mentioned in README
was targeted by lz4 upstream days ago.
Update README so all users can be noticed.
Signed-off-by: Gao Xiang <hsiangkao@aol.com>
---
README | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/README b/README
index 60b8eed6c1d3..5addd6b80e04 100644
--- a/README
+++ b/README
@@ -78,6 +78,11 @@ Known issues
LZ4_compress_HC_destSize()
https://github.com/lz4/lz4/issues/784
+ which has been resolved in
+ https://github.com/lz4/lz4/commit/e7fe105ac6ed02019d34731d2ba3aceb11b51bb1
+
+ and will be included in lz4-1.9.3 if all goes well.
+
Obsoleted erofs.mkfs
~~~~~~~~~~~~~~~~~~~~
--
2.24.0
next parent reply other threads:[~2020-10-12 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201012073446.18103-1-hsiangkao.ref@aol.com>
2020-10-12 7:34 ` Gao Xiang via Linux-erofs [this message]
2020-10-12 15:21 ` [PATCH] erofs-utils: README: update known-issue status of lz4hc Li GuiFu via Linux-erofs
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=20201012073446.18103-1-hsiangkao@aol.com \
--to=linux-erofs@lists.ozlabs.org \
--cc=hsiangkao@aol.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;
as well as URLs for NNTP newsgroup(s).