[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0891a316-1a62-4236-bfae-6fbb4f5341cf@linux.ibm.com>
Date: Tue, 21 Nov 2023 17:02:44 -0500
From: Tony Krowiak <akrowiak@...ux.ibm.com>
To: Alexander Gordeev <agordeev@...ux.ibm.com>,
Christian Borntraeger <borntraeger@...ux.ibm.com>
Cc: linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, Vasily Gorbik <gor@...ux.ibm.com>,
Heiko Carstens <hca@...ux.ibm.com>, jjherne@...ux.ibm.com,
pasic@...ux.ibm.com, frankja@...ux.ibm.com, imbrenda@...ux.ibm.com,
david@...hat.com, Harald Freudenberger <freude@...ux.ibm.com>
Subject: Re: [PATCH v2] s390/vfio-ap: fix sysfs status attribute for AP queue
devices
On 11/21/23 09:36, Alexander Gordeev wrote:
> On Mon, Nov 20, 2023 at 10:16:10AM +0100, Christian Borntraeger wrote:
>> I think this can go via the s390 tree as well. Alexander do you want to take it?
>
> Applied, thanks!
>
> I assume, it does not need to wait until the merge window?
I can't answer that question, but this is not a critical fix as it
simply fixes an erroneous display of a queue's status via it's sysfs
status attribute which is reflected in the lszcrypt -V output. The error
only occurs in a specific instance which is likely rare.
Powered by blists - more mailing lists