linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Freudenberger <freude@linux.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, linux-s390@vger.kernel.org,
	dengler@linux.ibm.com, ifranzki@linux.ibm.com,
	fcallies@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com,
	agordeev@linux.ibm.com
Subject: Re: [PATCH v12 0/6] New s390 specific protected key hmac
Date: Wed, 25 Jun 2025 11:04:28 +0200	[thread overview]
Message-ID: <247f28660259444c0293e24b151f508c@linux.ibm.com> (raw)

On 2025-06-24 13:37, Herbert Xu wrote:
> On Tue, Jun 24, 2025 at 01:34:41PM +0200, Harald Freudenberger wrote:
>> 
>> as the phmac implementation uses the newly introduced 
>> CRYPTO_ALG_NO_FALLBACK
>> flag, we can't deliver this patch series via s390. I talked with Heiko
>> about that and there are two options:
>> 1) We (s390) pick your patch 4ccd065a69df ("crypto: ahash - Add 
>> support for
>>    drivers with no fallback") together with my patch series for the 
>> next
>>    kernel's merge window.
>> 2) You (crypto) pick my patch series into your cryptodev-2.6 for next
>>    kernel's merge window.
>> I would prefer option 2 as most of the patches anyway deal with crypto
>> and Heiko and I do not expect unsolvable merge conflicts with the next
>> kernel's merge.
>> So what is your opinion?
> 
> Sure I can do that if you wish.  Is it just that series or are
> there other dependencies that I need first?
> 
> Cheers,

Thanks this would be great.
No there are no other dependencies, all required code has been merged
into 6.16 already. So for the 6.17 merge window the phmac patch series
v12 has all tags correct and should apply without any problems.



             reply	other threads:[~2025-06-25  9:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25  9:04 Harald Freudenberger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-17 13:44 [PATCH v12 0/6] New s390 specific protected key hmac Harald Freudenberger
2025-06-18  8:58 ` Herbert Xu
2025-06-24 11:34 ` Harald Freudenberger
2025-06-24 11:37   ` Herbert Xu
2025-06-26 10:54 ` 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=247f28660259444c0293e24b151f508c@linux.ibm.com \
    --to=freude@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=dengler@linux.ibm.com \
    --cc=fcallies@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=ifranzki@linux.ibm.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-s390@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;
as well as URLs for NNTP newsgroup(s).