From: akpm@linux-foundation.org
To: hsiangkao@redhat.com, joe@perches.com,
mm-commits@vger.kernel.org, terrelln@fb.com,
thisisrast7@gmail.com
Subject: [merged] lz4_decompress-declare-lz4_decompress_safe_withprefix64k-static.patch removed from -mm tree
Date: Tue, 06 Jul 2021 12:22:51 -0700 [thread overview]
Message-ID: <20210706192251.qzgokR6Oz%akpm@linux-foundation.org> (raw)
The patch titled
Subject: lz4_decompress: declare LZ4_decompress_safe_withPrefix64k static
has been removed from the -mm tree. Its filename was
lz4_decompress-declare-lz4_decompress_safe_withprefix64k-static.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Rajat Asthana <thisisrast7@gmail.com>
Subject: lz4_decompress: declare LZ4_decompress_safe_withPrefix64k static
Declare LZ4_decompress_safe_withPrefix64k as static to fix sparse
warning:
> warning: symbol 'LZ4_decompress_safe_withPrefix64k' was not declared.
> Should it be static?
Link: https://lkml.kernel.org/r/20210511154345.610569-1-thisisrast7@gmail.com
Signed-off-by: Rajat Asthana <thisisrast7@gmail.com>
Reviewed-by: Nick Terrell <terrelln@fb.com>
Cc: Gao Xiang <hsiangkao@redhat.com>
Cc: Joe Perches <joe@perches.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/lz4/lz4_decompress.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/lib/lz4/lz4_decompress.c~lz4_decompress-declare-lz4_decompress_safe_withprefix64k-static
+++ a/lib/lz4/lz4_decompress.c
@@ -481,7 +481,7 @@ int LZ4_decompress_fast(const char *sour
/* ===== Instantiate a few more decoding cases, used more than once. ===== */
-int LZ4_decompress_safe_withPrefix64k(const char *source, char *dest,
+static int LZ4_decompress_safe_withPrefix64k(const char *source, char *dest,
int compressedSize, int maxOutputSize)
{
return LZ4_decompress_generic(source, dest,
_
Patches currently in -mm which might be from thisisrast7@gmail.com are
reply other threads:[~2021-07-06 19:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210706192251.qzgokR6Oz%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hsiangkao@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=terrelln@fb.com \
--cc=thisisrast7@gmail.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.