From: karthik@techveda.org
To: gilad@benyossef.com, gregkh@linuxfoundation.org
Cc: linux-crypto@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
sunil.m@techveda.org, Karthik Tummala <karthik@techveda.org>
Subject: [PATCH 0/2] staging: ccree: Fix coding style and remove warnings
Date: Wed, 28 Jun 2017 15:07:11 +0530 [thread overview]
Message-ID: <1498642633-3260-1-git-send-email-karthik@techveda.org> (raw)
From: Karthik Tummala <karthik@techveda.org>
This patch series fixes coding style and removes the following
checkpatch.pl warnings:
Prefer using '"%s...", __func__' to using the function's name,
in a string.
Braces {} are not necessary for single statement blocks.
Rebased on top of next-20170627.
Patches were tested and built on next-20170627
Karthik Tummala (2):
staging: ccree: Use __func__ instead of function name
staging: ccree: Remove braces {} for single statement blocks
drivers/staging/ccree/ssi_aead.c | 48 ++++++++++++++++------------------------
1 file changed, 19 insertions(+), 29 deletions(-)
--
1.9.1
next reply other threads:[~2017-06-28 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 9:37 karthik [this message]
2017-06-28 9:37 ` [PATCH 1/2] staging: ccree: Use __func__ instead of function name karthik
2017-06-28 9:37 ` [PATCH 2/2] staging: ccree: Remove braces {} for single statement blocks karthik
2017-06-28 9:45 ` [PATCH 0/2] staging: ccree: Fix coding style and remove warnings Gilad Ben-Yossef
2017-06-29 10:43 ` karthik
2017-06-29 14:18 ` Greg Kroah-Hartman
2017-06-29 17:08 ` [PATCH v2] staging: ccree: Use __func__ instead of function name karthik
2017-07-11 13:40 ` Gilad Ben-Yossef
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=1498642633-3260-1-git-send-email-karthik@techveda.org \
--to=karthik@techveda.org \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gilad@benyossef.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sunil.m@techveda.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;
as well as URLs for NNTP newsgroup(s).