From: Vasily Gorbik <gor@linux.ibm.com>
To: Finn Callies <fcallies@linux.ibm.com>
Cc: hca@linux.ibm.com, agordeev@linux.ibm.com,
linux-s390@vger.kernel.org, freude@linux.ibm.com
Subject: Re: [PATCH v1 0/1] Fix the length of the qd field of the TAPQ response
Date: Wed, 29 Jul 2026 13:25:47 +0200 [thread overview]
Message-ID: <ttixp2z@ub.hpns> (raw)
In-Reply-To: <20260723150038.93617-1-fcallies@linux.ibm.com>
On Thu, Jul 23, 2026 at 05:00:37PM +0200, Finn Callies wrote:
> ====== CHANGELOG ======
>
> v1:
> - initial version
> - review from Harald
>
> Finn Callies (1):
> s390/ap: Fix queue depth field length
>
> arch/s390/include/asm/ap.h | 4 ++--
> drivers/s390/crypto/ap_bus.h | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
Applied, thank you!
prev parent reply other threads:[~2026-07-29 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 15:00 [PATCH v1 0/1] Fix the length of the qd field of the TAPQ response Finn Callies
2026-07-23 15:00 ` [PATCH v1 1/1] s390/ap: Fix queue depth field length Finn Callies
2026-07-23 15:13 ` sashiko-bot
2026-07-29 11:25 ` Vasily Gorbik [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=ttixp2z@ub.hpns \
--to=gor@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=fcallies@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=hca@linux.ibm.com \
--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