From: "Horia Geantă" <horia.geanta@nxp.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>,
Aymen Sghaier <aymen.sghaier@nxp.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] crypto: caam - fix typo
Date: Thu, 4 Jun 2020 13:08:43 +0300 [thread overview]
Message-ID: <d32a1b32-ce88-3286-4e6c-3280150f4d54@nxp.com> (raw)
In-Reply-To: <20200604024013.5669-1-xypron.glpk@gmx.de>
On 6/4/2020 5:41 AM, Heinrich Schuchardt wrote:
> %s/suppying/supplying/
>
This is good since it's not detected by the default kernel spellchecker.
Would you be willing to append also the detected typos?
CHECK: 'interrrupt' may be misspelled - perhaps 'interrupt'?
#57: FILE: drivers/crypto/caam/ctrl.c:57:
+ * resets the done interrrupt and returns the RNG to idle.
CHECK: 'occured' may be misspelled - perhaps 'occurred'?
#159: FILE: drivers/crypto/caam/ctrl.c:159:
+ * If an error occured in the descriptor, then
CHECK: 'aquired' may be misspelled - perhaps 'acquired'?
#267: FILE: drivers/crypto/caam/ctrl.c:267:
+ * entropy being aquired.
CHECK: 'paramters' may be misspelled - perhaps 'parameters'?
#736: FILE: drivers/crypto/caam/ctrl.c:736:
+ * Read the Compile Time paramters and SCFGR to determine
CHECK: 'modfiy' may be misspelled - perhaps 'modify'?
#866: FILE: drivers/crypto/caam/ctrl.c:866:
+ * and the kick_trng(...) function will modfiy the
CHECK: 'sucessful' may be misspelled - perhaps 'successful'?
#868: FILE: drivers/crypto/caam/ctrl.c:868:
+ * interval, leading to a sucessful initialization of
CHECK: 'Propogate' may be misspelled - perhaps 'Propagate'?
#116: FILE: drivers/crypto/caam/desc.h:116:
+/* Propogate DNR property to SharedDesc */
CHECK: 'defintions' may be misspelled - perhaps 'definitions'?
#456: FILE: drivers/crypto/caam/pdb.h:456:
+ u32 sgf_ln; /* Use DSA_PDB_ defintions per above */
Thanks,
Horia
next prev parent reply other threads:[~2020-06-04 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 2:40 Heinrich Schuchardt
2020-06-04 10:08 ` Horia Geantă [this message]
2020-06-12 6:47 ` Herbert Xu
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=d32a1b32-ce88-3286-4e6c-3280150f4d54@nxp.com \
--to=horia.geanta@nxp.com \
--cc=aymen.sghaier@nxp.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xypron.glpk@gmx.de \
/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®