From: karthik <karthik@techveda.org>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-crypto@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
sunil.m@techveda.org
Subject: Re: [PATCH 0/2] staging: ccree: Fix coding style and remove warnings
Date: Thu, 29 Jun 2017 16:13:38 +0530 [thread overview]
Message-ID: <1f681a83-4413-8c9d-ab75-c223b6c8b55b@techveda.org> (raw)
In-Reply-To: <CAOtvUMdpwFaMDh2qCnB=keZQAc6ssXM+u39GPaf0ASGr002OJA@mail.gmail.com>
On Wednesday 28 June 2017 03:15 PM, Gilad Ben-Yossef wrote:
> Thank you Karthik,
>
> On Wed, Jun 28, 2017 at 12:37 PM, <karthik@techveda.org> wrote:
>> 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.
>
> This one is good.
>>
>> Braces {} are not necessary for single statement blocks.
>
> I have already sent a patch addressing this and some other things
> yesterday/
>
>>
>> Rebased on top of next-20170627.
>> Patches were tested and built on next-20170627
>
> Can you please check patch 1 still applies after yesterdays patch series?
Hi, I have applied your patch series and then tried to apply patch 1 and
it failed. Should I wait until the patch series gets accepted and then
continue my work on the new linux-next release ? or is there any other
option ?
>
>>
>> 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
>>
>
> Thanks,
> Gilad
>
Thanks
karthik
next prev parent reply other threads:[~2017-06-29 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 9:37 [PATCH 0/2] staging: ccree: Fix coding style and remove warnings karthik
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 [this message]
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=1f681a83-4413-8c9d-ab75-c223b6c8b55b@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).