All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: f2fs crypto: filename encryption facilities
Date: Tue, 12 May 2015 14:38:57 +0300	[thread overview]
Message-ID: <20150512113856.GA12780@mwanda> (raw)

Hello Jaegeuk Kim,

The patch c54316510133: "f2fs crypto: filename encryption facilities"
from Apr 26, 2015, leads to the following static checker warning:

	fs/f2fs/crypto_fname.c:189 f2fs_fname_decrypt()
	warn: passing __func__ while the format string already contains the name of the function 'f2fs_fname_decrypt'

fs/f2fs/crypto_fname.c
   187          ablkcipher_request_free(req);
   188          if (res < 0) {
   189                  printk_ratelimited(KERN_ERR
   190                          "%s: Error in f2fs_fname_decrypt (error code %d)\n",
                                              ^^^^^^^^^^^^^^^^^^
   191                          __func__, res);
                                ^^^^^^^^

   192                  return res;
   193          }

regards,
dan carpenter

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

             reply	other threads:[~2015-05-12 11:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 11:38 Dan Carpenter [this message]
2015-05-12 18:19 ` f2fs crypto: filename encryption facilities Jaegeuk Kim

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=20150512113856.GA12780@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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.