mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: AlanSong-oc <AlanSong-oc@zhaoxin.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	davem@davemloft.net, linux-crypto@vger.kernel.org,
	linux-kernel@vger.kernel.org, CobeChen@zhaoxin.com,
	TonyWWang-oc@zhaoxin.com, YunShen@zhaoxin.com,
	GeorgeXue@zhaoxin.com, LeoLiu-oc@zhaoxin.com, HansHu@zhaoxin.com,
	Larry Wei <larryw3i@yeah.net>,
	1113996@bugs.debian.org
Subject: Re: [PATCH] crypto: padlock-sha - Add support for Zhaoxin processor
Date: Thu, 25 Sep 2025 22:23:30 +0200	[thread overview]
Message-ID: <aNWkwiHk7sFkHEVp@eldamar.lan> (raw)
In-Reply-To: <bcaaccf4-4048-48a0-a9f9-64902a16a049@zhaoxin.com>

Hi,

On Wed, Jun 25, 2025 at 09:51:56AM +0800, AlanSong-oc wrote:
> On 6/23/2025 5:24 PM, Herbert Xu wrote:
> > Thanks for the explanation.  There is no requirement to use struct
> > sha1_state.  Just supply a custom version of the struct for the
> > shash descriptor that includes the necessary space.
> > 
> > IOW do the copy in the rarely used export/import functions, instead
> > of on every hash operation.
> 
> Sorry for the late reply. Thank you for your suggestion and review.
> 
> I will send an updated patch soon.

FWIW, Larry Wei reported this issue as well in a separate Debian bug
report at https://bugs.debian.org/1113996 .

So far there was no patch applied to mainline if I'm correct. Did that
felt through the cracks?

Regards,
Salvatore

      reply	other threads:[~2025-09-25 20:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 10:17 AlanSong-oc
2025-06-12  5:05 ` Herbert Xu
2025-06-16 12:23   ` AlanSong-oc
2025-06-23  9:24     ` Herbert Xu
2025-06-25  1:51       ` AlanSong-oc
2025-09-25 20:23         ` Salvatore Bonaccorso [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=aNWkwiHk7sFkHEVp@eldamar.lan \
    --to=carnil@debian.org \
    --cc=1113996@bugs.debian.org \
    --cc=AlanSong-oc@zhaoxin.com \
    --cc=CobeChen@zhaoxin.com \
    --cc=GeorgeXue@zhaoxin.com \
    --cc=HansHu@zhaoxin.com \
    --cc=LeoLiu-oc@zhaoxin.com \
    --cc=TonyWWang-oc@zhaoxin.com \
    --cc=YunShen@zhaoxin.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=larryw3i@yeah.net \
    --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®