From: Nick Terrell <terrelln@meta.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nick Terrell <terrelln@meta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nick Terrell <nickrterrell@gmail.com>
Subject: [GIT PULL] zstd changes for v6.3-rc1
Date: Fri, 3 Mar 2023 06:23:41 +0000 [thread overview]
Message-ID: <C8C4DFDA-998F-48AD-93C9-DE16F8080A02@meta.com> (raw)
The following changes since commit c9c3395d5e3dcc6daee66c6908354d47bf98cb0c:
Linux 6.2 (2023-02-19 14:24:22 -0800)
are available in the Git repository at:
https://github.com/terrelln/linux.git tags/zstd-linus-v6.3
for you to fetch changes up to 9844ed7e93967c0eaa27cab2fc80583e38696a0e:
Merge tag 'v6.2' into zstd-linus (2023-03-02 22:15:55 -0800)
----------------------------------------------------------------
Zstd fixes for v6.3
A small number of fixes for zstd-v1.5.2.
I'm not pulling in zstd-v1.5.4 from upstream this release because it
didn't have any time to bake in linux-next, but I'm aiming for the next
update in v6.4.
Signed-off-by: Nick Terrell <terrelln@fb.com>
----------------------------------------------------------------
Enrico Scholz (1):
zstd: fix assert() logic
Kees Cook (1):
lib: zstd: Fix -Wstringop-overflow warning
Nick Terrell (3):
Merge branch 'main' into zstd-linus
lib: zstd: Backport fix for in-place decompression
Merge tag 'v6.2' into zstd-linus
lib/zstd/common/zstd_deps.h | 2 +-
lib/zstd/decompress/huf_decompress.c | 2 +-
lib/zstd/decompress/zstd_decompress.c | 25 ++++++++++++++++++++++---
3 files changed, 24 insertions(+), 5 deletions(-)
next reply other threads:[~2023-03-03 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 6:23 Nick Terrell [this message]
2023-03-03 17:28 ` Linus Torvalds
2023-03-03 17:54 ` Nick Terrell
2023-03-03 17:59 ` Linus Torvalds
2023-03-03 18:03 ` Nick Terrell
2023-03-03 18:16 ` Linus Torvalds
2023-03-03 18:26 ` Nick Terrell
2023-03-03 18:48 ` Theodore Ts'o
2023-03-03 18:05 ` Linus Torvalds
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=C8C4DFDA-998F-48AD-93C9-DE16F8080A02@meta.com \
--to=terrelln@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickrterrell@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®