Linux-S390 Archive mirror
 help / color / mirror / Atom feed
From: Alexander Gordeev <agordeev@linux.ibm.com>
To: "Jason J. Herne" <jjherne@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
	pasic@linux.ibm.com, akrowiak@linux.ibm.com,
	borntraeger@de.ibm.com, gor@linux.ibm.com, hca@linux.ibm.com
Subject: Re: [PATCH v5 0/5] s390/vfio-ap: ap_config sysfs attribute for mdevctl automation
Date: Tue, 16 Apr 2024 11:00:03 +0200	[thread overview]
Message-ID: <Zh4+E9DkeQnPP52J@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com> (raw)
In-Reply-To: <20240415152555.13152-1-jjherne@linux.ibm.com>

On Mon, Apr 15, 2024 at 11:25:50AM -0400, Jason J. Herne wrote:
Hi Jason,
>  Documentation/arch/s390/vfio-ap.rst   |  30 ++++
>  drivers/s390/crypto/ap_bus.c          |  13 +-
>  drivers/s390/crypto/ap_bus.h          |  22 +++
>  drivers/s390/crypto/vfio_ap_ops.c     | 224 ++++++++++++++++++++++++--
>  drivers/s390/crypto/vfio_ap_private.h |   6 +-
>  5 files changed, 266 insertions(+), 29 deletions(-)

Applied, thanks!

      parent reply	other threads:[~2024-04-16  9:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 15:25 [PATCH v5 0/5] s390/vfio-ap: ap_config sysfs attribute for mdevctl automation Jason J. Herne
2024-04-15 15:25 ` [PATCH v5 1/5] s390/ap: Externalize AP bus specific bitmap reading function Jason J. Herne
2024-04-15 15:25 ` [PATCH v5 2/5] s390/vfio-ap: Add sysfs attr, ap_config, to export mdev state Jason J. Herne
2024-04-15 15:25 ` [PATCH v5 3/5] s390/vfio-ap: Ignore duplicate link requests in vfio_ap_mdev_link_queue Jason J. Herne
2024-04-15 15:25 ` [PATCH v5 4/5] s390/vfio-ap: Add write support to sysfs attr ap_config Jason J. Herne
2024-04-15 15:25 ` [PATCH v5 5/5] docs: Update s390 vfio-ap doc for ap_config sysfs attribute Jason J. Herne
2024-04-16  9:00 ` Alexander Gordeev [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=Zh4+E9DkeQnPP52J@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com \
    --to=agordeev@linux.ibm.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=jjherne@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).