linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Glauber <jan.glauber@cavium.com>
To: Colin King <colin.king@canonical.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	Robert Richter <rrichter@cavium.com>,
	linux-crypto@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: zip: make several functions static
Date: Mon, 2 Jul 2018 07:45:40 +0200	[thread overview]
Message-ID: <20180702054540.GA14359@hc> (raw)
In-Reply-To: <20180630113049.4402-1-colin.king@canonical.com>

Hi Colin,

I've already posted a similar patch:
https://patchwork.kernel.org/patch/10482283/

--Jan

On Sat, Jun 30, 2018 at 12:30:49PM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> The functions zip_ctx_exit, zip_compress, zip_decompress and zip_ctx_init
> are local to the source and do not need to be in global scope, so make
> them static.
> 
> Cleans up sparse warnings:
> symbol 'zip_ctx_exit' was not declared. Should it be static?
> symbol 'zip_compress' was not declared. Should it be static?
> symbol 'zip_decompress' was not declared. Should it be static?
> symbol 'zip_ctx_init' was not declared. Should it be static?
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  drivers/crypto/cavium/zip/zip_crypto.c | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/crypto/cavium/zip/zip_crypto.c b/drivers/crypto/cavium/zip/zip_crypto.c
> index b92b6e7e100f..f9e99a15d2a0 100644
> --- a/drivers/crypto/cavium/zip/zip_crypto.c
> +++ b/drivers/crypto/cavium/zip/zip_crypto.c
> @@ -69,7 +69,7 @@ static void zip_static_init_zip_ops(struct zip_operation *zip_ops,
>         zip_ops->csum         = 1; /* Adler checksum desired */
>  }
> 
> -int zip_ctx_init(struct zip_kernel_ctx *zip_ctx, int lzs_flag)
> +static int zip_ctx_init(struct zip_kernel_ctx *zip_ctx, int lzs_flag)
>  {
>         struct zip_operation  *comp_ctx   = &zip_ctx->zip_comp;
>         struct zip_operation  *decomp_ctx = &zip_ctx->zip_decomp;
> @@ -107,7 +107,7 @@ int zip_ctx_init(struct zip_kernel_ctx *zip_ctx, int lzs_flag)
>         return -ENOMEM;
>  }
> 
> -void zip_ctx_exit(struct zip_kernel_ctx *zip_ctx)
> +static void zip_ctx_exit(struct zip_kernel_ctx *zip_ctx)
>  {
>         struct zip_operation  *comp_ctx   = &zip_ctx->zip_comp;
>         struct zip_operation  *dec_ctx = &zip_ctx->zip_decomp;
> @@ -119,9 +119,9 @@ void zip_ctx_exit(struct zip_kernel_ctx *zip_ctx)
>         zip_data_buf_free(dec_ctx->output, MAX_OUTPUT_BUFFER_SIZE);
>  }
> 
> -int zip_compress(const u8 *src, unsigned int slen,
> -                u8 *dst, unsigned int *dlen,
> -                struct zip_kernel_ctx *zip_ctx)
> +static int zip_compress(const u8 *src, unsigned int slen,
> +                       u8 *dst, unsigned int *dlen,
> +                       struct zip_kernel_ctx *zip_ctx)
>  {
>         struct zip_operation  *zip_ops   = NULL;
>         struct zip_state      *zip_state;
> @@ -155,9 +155,9 @@ int zip_compress(const u8 *src, unsigned int slen,
>         return ret;
>  }
> 
> -int zip_decompress(const u8 *src, unsigned int slen,
> -                  u8 *dst, unsigned int *dlen,
> -                  struct zip_kernel_ctx *zip_ctx)
> +static int zip_decompress(const u8 *src, unsigned int slen,
> +                         u8 *dst, unsigned int *dlen,
> +                         struct zip_kernel_ctx *zip_ctx)
>  {
>         struct zip_operation  *zip_ops   = NULL;
>         struct zip_state      *zip_state;
> --
> 2.17.1

      reply	other threads:[~2018-07-02  5:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30 11:30 [PATCH] crypto: zip: make several functions static Colin King
2018-07-02  5:45 ` Jan Glauber [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=20180702054540.GA14359@hc \
    --to=jan.glauber@cavium.com \
    --cc=colin.king@canonical.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rrichter@cavium.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).