From: srishti sharma <srishtishar@gmail.com>
To: gregkh@linuxfoundation.org
Cc: gilad@benyossef.com, linux-crypto@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
srishti sharma <srishtishar@gmail.com>
Subject: [PATCH 1/4] Staging: ccree: cc_crypto_ctx.h: Added * on subsequent lines of a comment block.
Date: Sun, 4 Jun 2017 05:02:08 +0530 [thread overview]
Message-ID: <e1974f1fece258f422e8f90ca820170a2b982933.1496531673.git.srishtishar@gmail.com> (raw)
In-Reply-To: <cover.1496531673.git.srishtishar@gmail.com>
Added * on subsequent lines of a comment block.
Signed-off-by: srishti sharma <srishtishar@gmail.com>
---
drivers/staging/ccree/cc_crypto_ctx.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/ccree/cc_crypto_ctx.h b/drivers/staging/ccree/cc_crypto_ctx.h
index ac39d34..6ee51b8 100644
--- a/drivers/staging/ccree/cc_crypto_ctx.h
+++ b/drivers/staging/ccree/cc_crypto_ctx.h
@@ -219,7 +219,7 @@ struct drv_ctx_hash {
};
/* !!!! drv_ctx_hmac should have the same structure as drv_ctx_hash except
- k0, k0_size fields */
+ * k0, k0_size fields */
struct drv_ctx_hmac {
enum drv_crypto_alg alg; /* DRV_CRYPTO_ALG_HMAC */
enum drv_hash_mode mode;
--
2.7.4
next prev parent reply other threads:[~2017-06-03 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 23:31 [PATCH 0/4] Fixed comment coding style issues srishti sharma
2017-06-03 23:32 ` srishti sharma [this message]
2017-06-04 8:19 ` [PATCH 1/4] Staging: ccree: cc_crypto_ctx.h: Added * on subsequent lines of a comment block Greg KH
2017-06-06 13:40 ` srishti sharma
2017-06-03 23:32 ` [PATCH 2/4] Staging: ccree: cc_crypto_ctx.h: Fixed trailing */ issue in " srishti sharma
2017-06-03 23:33 ` [PATCH 3/4] Staging: ccree: cc_crypto_ctx.h: Fixed * alignment issues " srishti sharma
2017-06-03 23:33 ` [PATCH 4/4] Staging: ccree: cc_crypto_ctx.h: Added * on subsequent lines of " srishti sharma
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=e1974f1fece258f422e8f90ca820170a2b982933.1496531673.git.srishtishar@gmail.com \
--to=srishtishar@gmail.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 \
/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
all inboxes | Powered by JetHome®