public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rajat Asthana <thisisrast7@gmail.com>
To: akpm@linux-foundation.org, terrelln@fb.com, hsiangkao@redhat.com,
	joe@perches.com
Cc: linux-kernel@vger.kernel.org, Rajat Asthana <thisisrast7@gmail.com>
Subject: [PATCH] lz4_decompress: declare LZ4_decompress_safe_withPrefix64k static
Date: Tue, 11 May 2021 21:13:45 +0530	[thread overview]
Message-ID: <20210511154345.610569-1-thisisrast7@gmail.com> (raw)

Declare LZ4_decompress_safe_withPrefix64k as static to fix sparse
warning:

> warning: symbol 'LZ4_decompress_safe_withPrefix64k' was not declared.
> Should it be static?

Signed-off-by: Rajat Asthana <thisisrast7@gmail.com>
---
 lib/lz4/lz4_decompress.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/lz4/lz4_decompress.c b/lib/lz4/lz4_decompress.c
index 8a7724a6ce2f..926f4823d5ea 100644
--- a/lib/lz4/lz4_decompress.c
+++ b/lib/lz4/lz4_decompress.c
@@ -481,7 +481,7 @@ int LZ4_decompress_fast(const char *source, char *dest, int originalSize)
 
 /* ===== 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,
-- 
2.31.1


             reply	other threads:[~2021-05-11 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 15:43 Rajat Asthana [this message]
2021-05-11 19:33 ` [PATCH] lz4_decompress: declare LZ4_decompress_safe_withPrefix64k static Nick Terrell

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=20210511154345.610569-1-thisisrast7@gmail.com \
    --to=thisisrast7@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hsiangkao@redhat.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=terrelln@fb.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