From: Marek Vasut <marex@denx.de>
To: "Horia Geantă" <horia.geanta@freescale.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>, linux-crypto@vger.kernel.org
Subject: Re: [PATCH cryptodev 1/4] crypto: caam - remove error propagation handling
Date: Wed, 19 Mar 2014 20:01:56 +0100 [thread overview]
Message-ID: <201403192001.56356.marex@denx.de> (raw)
In-Reply-To: <5329D31C.6030807@freescale.com>
On Wednesday, March 19, 2014 at 06:25:48 PM, Horia Geantă wrote:
> On 3/17/2014 8:23 PM, Marek Vasut wrote:
> > On Friday, March 14, 2014 at 04:46:49 PM, Horia Geanta wrote:
> >> Commit 61bb86bba169507a5f223b94b9176c32c84b4721
> >> ("crypto: caam - set descriptor sharing type to SERIAL")
> >> changed the descriptor sharing mode from SHARE_WAIT to SHARE_SERIAL.
> >>
> >> All descriptor commands that handle the "ok to share" and
> >> "error propagation" settings should also go away, since they have no
> >> meaning for SHARE_SERIAL.
> >
> > [...]
> >
> >> @@ -253,7 +236,7 @@ static int aead_set_sh_desc(struct crypto_aead
> >> *aead)
> >>
> >> /* assoclen + cryptlen = seqinlen - ivsize */
> >> append_math_sub_imm_u32(desc, REG2, SEQINLEN, IMM, tfm->ivsize);
> >>
> >> - /* assoclen + cryptlen = (assoclen + cryptlen) - cryptlen */
> >> + /* assoclen = (assoclen + cryptlen) - cryptlen */
> >
> > This comment basically says 'x = x' , but it doesn't explain anything to
> > uninformed observer. Can you fix such comments please ?
>
> The line under the comment is:
> append_math_sub(desc, VARSEQINLEN, REG2, REG3, CAAM_CMD_SZ);
>
> which translates to:
> VARSEQINLEN = REG2 - REG3
>
> The comment basically says that VARSEQINLEN gets assoclen by
> substracting REG3 = cryptlen from REG2 = assoclen + cryptlen.
>
> If you still think this is "cryptic", that's perfectly fine - I'll
> respin the patch.
OK, I don't get it anyway. But that's OK, I am sure the next Marek that comes
across this code won't get it either. So I'd suggest you produce a patch
afterwards, which cleans up the documentation ugliness in this driver. Would
that work for you?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-03-19 19:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 15:46 [PATCH cryptodev 1/4] crypto: caam - remove error propagation handling Horia Geanta
2014-03-14 15:46 ` [PATCH cryptodev 2/4] crypto: export NULL algorithms defines Horia Geanta
2014-03-14 15:46 ` [PATCH cryptodev 3/4] crypto: testmgr - add aead null encryption test vectors Horia Geanta
2014-03-17 18:27 ` Marek Vasut
2014-03-19 18:10 ` Horia Geantă
2014-03-14 15:46 ` [PATCH cryptodev 4/4] crypto: caam - add support for aead null encryption Horia Geanta
2014-03-17 18:23 ` [PATCH cryptodev 1/4] crypto: caam - remove error propagation handling Marek Vasut
2014-03-19 17:25 ` Horia Geantă
2014-03-19 19:01 ` Marek Vasut [this message]
2014-03-20 9:44 ` Horia Geantă
2014-03-21 14:40 ` 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=201403192001.56356.marex@denx.de \
--to=marex@denx.de \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@freescale.com \
--cc=linux-crypto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.