From: T Pratham <t-pratham@ti.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Manorit Chawdhry <m-chawdhry@ti.com>,
"Shiva Tripathi" <s-tripathi1@ti.com>,
Sebin Francis <sebin.francis@ti.com>,
"Vishal Mahaveer" <vishalm@ti.com>,
Praneeth Bajjuri <praneeth@ti.com>
Subject: Re: [PATCH v5 0/3] Add support for hashing algorithms in TI DTHE V2
Date: Wed, 19 Aug 2026 13:09:14 +0530 [thread overview]
Message-ID: <b2d9bced-9ffe-4ff2-87d8-20ac9aab33cf@ti.com> (raw)
In-Reply-To: <an-8NYJ1vo03NpRX@gondor.apana.org.au>
On 8/15/26 06:39, Herbert Xu wrote:
> On Fri, Aug 07, 2026 at 04:34:56PM +0530, T Pratham wrote:
>>
>> T Pratham (3):
>> crypto: ti - Add support for SHA224/256/384/512 in DTHEv2 driver
>> crypto: ti - Add support for MD5 in DTHEv2 Hashing Engine driver
>
> As even sha1 is being phased out, there is no point int adding
> another new implementation of md5 into the kernel.
>
> Please drop the md5 code.
Ok.
>
>> crypto: ti - Add support for HMAC in DTHEv2 Hashing Engine driver
>
> Sashiko has found some issues with this patch-set, please take
> a look:
>
> https://sashiko.dev/#/patchset/20260807110501.975130-1-t-pratham%40ti.com
Will look into this and update. Thanks.
--
Regards
T Pratham <t-pratham@ti.com>
prev parent reply other threads:[~2026-08-19 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 11:04 T Pratham
2026-08-07 11:04 ` [PATCH v5 1/3] crypto: ti - Add support for SHA224/256/384/512 in DTHEv2 driver T Pratham
2026-08-07 11:04 ` [PATCH v5 2/3] crypto: ti - Add support for MD5 in DTHEv2 Hashing Engine driver T Pratham
2026-08-07 11:04 ` [PATCH v5 3/3] crypto: ti - Add support for HMAC " T Pratham
2026-08-15 1:09 ` [PATCH v5 0/3] Add support for hashing algorithms in TI DTHE V2 Herbert Xu
2026-08-19 7:39 ` T Pratham [this message]
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=b2d9bced-9ffe-4ff2-87d8-20ac9aab33cf@ti.com \
--to=t-pratham@ti.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=praneeth@ti.com \
--cc=s-tripathi1@ti.com \
--cc=sebin.francis@ti.com \
--cc=vishalm@ti.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
all inboxes | Powered by JetHome®