linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Krowiak <akrowiak@linux.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: cohuck@redhat.com, pasic@linux.vnet.ibm.com,
	jjherne@linux.ibm.com, jgg@nvidia.com,
	alex.williamson@redhat.com, kwankhede@nvidia.com,
	frankja@linux.ibm.com, david@redhat.com, imbrenda@linux.ibm.com,
	hca@linux.ibm.com
Subject: Re: [PATCH v6 2/2] s390/vfio-ap: r/w lock for PQAP interception handler function pointer
Date: Wed, 7 Jul 2021 13:16:59 -0400	[thread overview]
Message-ID: <d6389aab-f6ad-1f48-5997-783c57201f3d@linux.ibm.com> (raw)
In-Reply-To: <53181dcb-cabc-d6a1-3bbe-7eba298f06fe@de.ibm.com>



On 7/1/21 11:25 AM, Christian Borntraeger wrote:
> On 30.06.21 17:18, Tony Krowiak wrote:
>> I assumed that this patch would get queued along with the other one 
>> in this series,
>> but it looks like that was an erroneous assumption. Should this also 
>> be queued?
>
> Sorry, this is on my todo list.


I rolled this up into the patch I posted today:
Message ID: <20210707154156.297139-1-akrowiak@linux.ibm.com>
s390/vfio-ap: do not open code locks for VFIO_GROUP_NOTIFY_SET_KVM 
notification


  parent reply	other threads:[~2021-07-07 17:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 15:57 [PATCH v6 0/2] s390/vfio-ap: fix memory leak in mdev remove callback Tony Krowiak
2021-06-21 15:57 ` [PATCH v6 1/2] s390/vfio-ap: clean up mdev resources when remove callback invoked Tony Krowiak
2021-06-21 16:04   ` Christian Borntraeger
2021-06-21 17:27     ` Jason Gunthorpe
2021-06-21 15:57 ` [PATCH v6 2/2] s390/vfio-ap: r/w lock for PQAP interception handler function pointer Tony Krowiak
2021-06-30 15:18   ` Tony Krowiak
2021-07-01 15:25     ` Christian Borntraeger
2021-07-01 16:28       ` Tony Krowiak
2021-07-07 17:16       ` Tony Krowiak [this message]
2021-07-01 15:13   ` Tony Krowiak

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=d6389aab-f6ad-1f48-5997-783c57201f3d@linux.ibm.com \
    --to=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=jgg@nvidia.com \
    --cc=jjherne@linux.ibm.com \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.vnet.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 NNTP newsgroup(s).