From: Joe Perches <joe@perches.com>
To: Gilad Ben-Yossef <gilad@benyossef.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ofir Drang <ofir.drang@arm.com>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org
Subject: Re: [PATCH v2 01/20] staging: ccree: remove spurious blank lines
Date: Thu, 01 Jun 2017 04:20:19 -0700 [thread overview]
Message-ID: <1496316019.2618.69.camel@perches.com> (raw)
In-Reply-To: <1496314993-30229-2-git-send-email-gilad@benyossef.com>
On Thu, 2017-06-01 at 14:02 +0300, Gilad Ben-Yossef wrote:
> Remove spurious blanks lines from cc_crypto_ctx.h file
unrelated trivia:
> diff --git a/drivers/staging/ccree/cc_crypto_ctx.h b/drivers/staging/ccree/cc_crypto_ctx.h
[]
> @@ -208,7 +204,6 @@ struct drv_ctx_generic {
> enum drv_crypto_alg alg;
> } __attribute__((__may_alias__));
Please try to remove the __may_alias__ attribute one day.
next prev parent reply other threads:[~2017-06-01 11:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 11:02 [PATCH v2 00/20] additional driver cleanups Gilad Ben-Yossef
2017-06-01 11:02 ` [PATCH v2 01/20] staging: ccree: remove spurious blank lines Gilad Ben-Yossef
2017-06-01 11:20 ` Joe Perches [this message]
2017-06-01 11:42 ` Joe Perches
2017-06-01 11:02 ` [PATCH v2 02/20] staging: ccree: replace bit shift with BIT macro Gilad Ben-Yossef
2017-06-03 8:46 ` Greg Kroah-Hartman
2017-06-04 5:31 ` Gilad Ben-Yossef
2017-06-01 11:02 ` [PATCH v2 03/20] staging: ccree: fix longer than 80 chars lines Gilad Ben-Yossef
2017-06-01 11:02 ` [PATCH v2 04/20] staging: ccree: fix operator spacing Gilad Ben-Yossef
2017-06-01 11:02 ` [PATCH v2 05/20] staging: ccree: fix comments formatting Gilad Ben-Yossef
2017-06-01 11:02 ` [PATCH v2 06/20] staging: ccree: add parentheses to macro argument Gilad Ben-Yossef
2017-06-01 11:02 ` [PATCH v2 07/20] staging: ccree: refactor HW command FIFO access Gilad Ben-Yossef
2017-06-01 11:02 ` [PATCH v2 08/20] staging: ccree: remove 48 bit dma addr sim Gilad Ben-Yossef
2017-06-01 11:02 ` [PATCH v2 09/20] staging: ccree: refactor LLI access macros Gilad Ben-Yossef
2017-06-01 11:03 ` [PATCH v2 10/20] staging: ccree: move M/LLI defines to header file Gilad Ben-Yossef
2017-06-01 11:03 ` [PATCH v2 11/20] staging: ccree: remove unused debug macros Gilad Ben-Yossef
2017-06-01 11:03 ` [PATCH v2 12/20] staging: ccree: remove cycle count debug support Gilad Ben-Yossef
2017-06-01 11:03 ` [PATCH v2 13/20] staging: ccree: move request_mgr to generic bitfield ops Gilad Ben-Yossef
2017-06-01 11:03 ` [PATCH v2 14/20] staging: ccree: remove custom bitfield macros Gilad Ben-Yossef
2017-06-01 11:03 ` [PATCH v2 15/20] staging: ccree: remove unused struct Gilad Ben-Yossef
2017-06-01 11:03 ` [PATCH v2 16/20] staging: ccree: use snake_case for hash enums Gilad Ben-Yossef
2017-06-01 11:03 ` [PATCH v2 17/20] staging: ccree: drop no longer used macro Gilad Ben-Yossef
2017-06-01 11:03 ` [PATCH v2 18/20] staging: ccree: remove dead code Gilad Ben-Yossef
2017-06-01 11:03 ` [PATCH v2 19/20] staging: ccree: remove spurious blank line Gilad Ben-Yossef
2017-06-01 11:03 ` [PATCH v2 20/20] staging: ccree: fix wrong whitespace usage 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=1496316019.2618.69.camel@perches.com \
--to=joe@perches.com \
--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=ofir.drang@arm.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
Powered by JetHome