From: Greg KH <gregkh@linuxfoundation.org>
To: Ammly Fredrick <ammlyf@gmail.com>
Cc: gilad@benyossef.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 12622/12622] Staging: ccree: ssi_cipher: fix brace coding style issue
Date: Sun, 14 May 2017 12:49:45 +0200 [thread overview]
Message-ID: <20170514104945.GB29758@kroah.com> (raw)
In-Reply-To: <20170513114503.5371-1-ammly@gmail.com>
On Sat, May 13, 2017 at 02:45:03PM +0300, Ammly Fredrick wrote:
> Fixed some coding style issues after running scripts/checkpatch.pl
>
> Fixed spelling in ssi_blkcipher_complete(), should be counter not couter.
>
> Signed-off-by: Ammly Fredrick <ammlyf@gmail.com>
I don't see the 12621 other patches in this series, did you really make
that many changes in this driver? :)
You are doing a lot of different things all in the same patch, which
isn't allowed. Please fix up and only do one type of thing at a time.
thanks,
greg k-h
prev parent reply other threads:[~2017-05-14 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 11:45 [PATCH 12622/12622] Staging: ccree: ssi_cipher: fix brace coding style issue Ammly Fredrick
2017-05-14 10:49 ` Greg KH [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=20170514104945.GB29758@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ammlyf@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gilad@benyossef.com \
--cc=linux-kernel@vger.kernel.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