Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <0a8aabe8-26c4-d530-9ba0-f7f177ba0afa@web.de>
In-Reply-To: <0a8aabe8-26c4-d530-9ba0-f7f177ba0afa@web.de>
From:   Gilad Ben-Yossef <gilad@benyossef.com>
Date:   Sun, 21 Jun 2020 14:16:01 +0300
Message-ID: <CAOtvUMcC9CP+NXG5MGM=-C5hS6WWbCEH6S207=i+0uL55cDZFA@mail.gmail.com>
Subject: Re: [PATCH 2/3] crypto: ccree: adapt ccree essiv support to kcapi
To:     Markus Elfring <Markus.Elfring@web.de>
Cc:     Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
        Linux kernel mailing list <linux-kernel@vger.kernel.org>,
        Ard Biesheuvel <ard.biesheuvel@linaro.org>,
        "David S. Miller" <davem@davemloft.net>,
        Herbert Xu <herbert@gondor.apana.org.au>,
        Libo Wang <libo.wang@arm.com>, Ofir Drang <ofir.drang@arm.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

Hi Markus,

On Sun, Jun 21, 2020 at 1:11 PM Markus Elfring <Markus.Elfring@web.de> wrot=
e:
>
> I propose to avoid a typo in the previous patch subject.
>
>
> > This patch brings the ccree essiv interface into
> > compliance with kernel crypto api one.
>
> Can an imperative wording be nicer for the commit message?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/D=
ocumentation/process/submitting-patches.rst?id=3D64677779e8962c20b580b47179=
0fe42367750599#n151
>

Thank you for the review and comments for this and the previous patch.

I have taken all your suggestions  into consideration and will include
them in the next revision of the patch set.

Thanks again,
Gilad

--=20
Gilad Ben-Yossef
Chief Coffee Drinker

values of =CE=B2 will give rise to dom!