From: Gilad Ben-Yossef <gilad@benyossef.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Joe Perches <joe@perches.com>, 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: [PATCH v3 10/18] staging: ccree: remove unused struct
Date: Sun, 4 Jun 2017 11:02:31 +0300 [thread overview]
Message-ID: <1496563362-7954-11-git-send-email-gilad@benyossef.com> (raw)
In-Reply-To: <1496563362-7954-1-git-send-email-gilad@benyossef.com>
struct SepHashPrivateContext is not used anywhere in the code.
Remove it.
Signed-off-by: Gilad Ben-Yossef <gilad@benyossef.com>
---
drivers/staging/ccree/hash_defs.h | 18 ------------------
1 file changed, 18 deletions(-)
diff --git a/drivers/staging/ccree/hash_defs.h b/drivers/staging/ccree/hash_defs.h
index 3f2b2d1..9e01219 100644
--- a/drivers/staging/ccree/hash_defs.h
+++ b/drivers/staging/ccree/hash_defs.h
@@ -57,23 +57,5 @@ enum HashCipherDoPadding {
HASH_CIPHER_DO_PADDING_RESERVE32 = S32_MAX,
};
-typedef struct SepHashPrivateContext {
- /* The current length is placed at the end of the context buffer because the hash
- * context is used for all HMAC operations as well. HMAC context includes a 64 bytes
- * K0 field. The size of struct drv_ctx_hash reserved field is 88/184 bytes depend if t
- * he SHA512 is supported ( in this case teh context size is 256 bytes).
- * The size of struct drv_ctx_hash reseved field is 20 or 52 depend if the SHA512 is supported.
- * This means that this structure size (without the reserved field can be up to 20 bytes ,
- * in case sha512 is not suppported it is 20 bytes (SEP_HASH_LENGTH_WORDS define to 2 ) and in the other
- * case it is 28 (SEP_HASH_LENGTH_WORDS define to 4)
- */
- u32 reserved[(sizeof(struct drv_ctx_hash)/sizeof(u32)) - SEP_HASH_LENGTH_WORDS - 3];
- u32 CurrentDigestedLength[SEP_HASH_LENGTH_WORDS];
- u32 KeyType;
- u32 dataCompleted;
- u32 hmacFinalization;
- /* no space left */
-} SepHashPrivateContext_s;
-
#endif /*_HASH_DEFS_H__*/
--
2.1.4
next prev parent reply other threads:[~2017-06-04 8:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 8:02 [PATCH v3 00/18] additional driver cleanups Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 01/18] staging: ccree: replace bit shift with BIT macro Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 02/18] staging: ccree: refactor HW command FIFO access Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 03/18] staging: ccree: remove 48 bit dma addr sim Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 04/18] staging: ccree: refactor LLI access macros Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 05/18] staging: ccree: move M/LLI defines to header file Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 06/18] staging: ccree: remove unused debug macros Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 07/18] staging: ccree: remove cycle count debug support Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 08/18] staging: ccree: move request_mgr to generic bitfield ops Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 09/18] staging: ccree: remove custom bitfield macros Gilad Ben-Yossef
2017-06-04 8:02 ` Gilad Ben-Yossef [this message]
2017-06-04 8:02 ` [PATCH v3 11/18] staging: ccree: use snake_case for hash enums Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 12/18] staging: ccree: drop no longer used macro Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 13/18] staging: ccree: remove dead code Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 14/18] staging: ccree: remove spurious blank line Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 15/18] staging: ccree: fix wrong whitespace usage Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 16/18] staging: ccree: remove last remnants of sash algo Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 17/18] staging: ccree: remove last remnants of sblkcipher Gilad Ben-Yossef
2017-06-04 8:02 ` [PATCH v3 18/18] staging: ccree: remove descriptor context definitions 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=1496563362-7954-11-git-send-email-gilad@benyossef.com \
--to=gilad@benyossef.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--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;
as well as URLs for NNTP newsgroup(s).