linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Cabiddu, Giovanni" <giovanni.cabiddu@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	<linux-mm@kvack.org>, Yosry Ahmed <yosry.ahmed@linux.dev>,
	Kanchana P Sridhar <kanchana.p.sridhar@intel.com>
Subject: Re: [v2 PATCH 0/7] crypto: acomp - Add request chaining and virtual address support
Date: Thu, 6 Mar 2025 12:14:16 +0000	[thread overview]
Message-ID: <Z8mRmCjVYo20o74P@gcabiddu-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <Z8jvbL8dbjsx83g1@gondor.apana.org.au>

On Thu, Mar 06, 2025 at 08:42:20AM +0800, Herbert Xu wrote:
> On Wed, Mar 05, 2025 at 09:37:43PM +0000, Cabiddu, Giovanni wrote:
> > 
> > What is the target tree for this set? It doesn't cleanly apply to
> > cryptodev.
> 
> It's based on the other two acomp patches in my queue:
> 
> https://patchwork.kernel.org/project/linux-crypto/list/
It is also dependent on `crypto: api - Move struct crypto_type into
internal.h`.

In case someone else wants to give it a go, this is the complete list of
dependencies:

  https://patchwork.kernel.org/project/linux-crypto/patch/Z71PHnpl0FeqChRE@gondor.apana.org.au/
  https://patchwork.kernel.org/project/linux-crypto/patch/aa2a2230a135b79b6f128d3a8beb21b49800e812.1740651138.git.herbert@gondor.apana.org.au/
  https://patchwork.kernel.org/project/linux-crypto/patch/bb32fbfe34c7f5f70dc5802d97e66ec88c470c66.1740651138.git.herbert@gondor.apana.org.au/

Regards,

-- 
Giovanni


  reply	other threads:[~2025-03-06 12:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04  9:25 Herbert Xu
2025-03-04  9:25 ` [v2 PATCH 1/7] crypto: api - Add cra_type->destroy hook Herbert Xu
2025-03-04  9:25 ` [v2 PATCH 2/7] crypto: scomp - Remove tfm argument from alloc/free_ctx Herbert Xu
2025-03-04  9:25 ` [v2 PATCH 3/7] crypto: acomp - Add request chaining and virtual addresses Herbert Xu
2025-03-04 21:59   ` Sridhar, Kanchana P
2025-03-05  1:51     ` Herbert Xu
2025-03-05 20:09       ` Sridhar, Kanchana P
2025-03-04  9:25 ` [v2 PATCH 4/7] crypto: testmgr - Remove NULL dst acomp tests Herbert Xu
2025-03-04  9:25 ` [v2 PATCH 5/7] crypto: scomp - Remove support for most non-trivial destination SG lists Herbert Xu
2025-03-04  9:25 ` [v2 PATCH 6/7] crypto: scomp - Add chaining and virtual address support Herbert Xu
2025-03-04  9:25 ` [v2 PATCH 7/7] crypto: acomp - Move stream management into scomp layer Herbert Xu
2025-03-05  1:46 ` [v2 PATCH 0/7] crypto: acomp - Add request chaining and virtual address support Jonathan Cameron
2025-03-05 21:37 ` Cabiddu, Giovanni
2025-03-06  0:42   ` Herbert Xu
2025-03-06 12:14     ` Cabiddu, Giovanni [this message]
2025-03-06  8:15 ` Ard Biesheuvel

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=Z8mRmCjVYo20o74P@gcabiddu-mobl.ger.corp.intel.com \
    --to=giovanni.cabiddu@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kanchana.p.sridhar@intel.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=yosry.ahmed@linux.dev \
    /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