From: Cornelia Huck <cohuck@redhat.com>
To: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, borntraeger@de.ibm.com,
bjsdjshi@linux.ibm.com, pasic@linux.ibm.com,
pmorel@linux.ibm.com
Subject: Re: [PATCH 1/1] vfio: ccw: fix error return in vfio_ccw_sch_event
Date: Wed, 2 May 2018 16:42:51 +0200 [thread overview]
Message-ID: <20180502164251.577e2af8.cohuck@redhat.com> (raw)
In-Reply-To: <20180502072559.50691-1-bjsdjshi@linux.vnet.ibm.com>
On Wed, 2 May 2018 09:25:59 +0200
Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> wrote:
> If device has not been registered, or there is a pending work,
s/a pending work/work pending/
> we should reschedule a sch_event call again.
>
> Signed-off-by: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
Slightly off-topic question: Is the mail address with or without the
'vnet' the one to go for?
> ---
> drivers/s390/cio/vfio_ccw_drv.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/s390/cio/vfio_ccw_drv.c b/drivers/s390/cio/vfio_ccw_drv.c
> index ea6a2d0b2894..770fa9cfc310 100644
> --- a/drivers/s390/cio/vfio_ccw_drv.c
> +++ b/drivers/s390/cio/vfio_ccw_drv.c
> @@ -177,6 +177,7 @@ static int vfio_ccw_sch_event(struct subchannel *sch, int process)
> {
> struct vfio_ccw_private *private = dev_get_drvdata(&sch->dev);
> unsigned long flags;
> + int rc = -EAGAIN;
>
> spin_lock_irqsave(sch->lock, flags);
> if (!device_is_registered(&sch->dev))
> @@ -187,6 +188,7 @@ static int vfio_ccw_sch_event(struct subchannel *sch, int process)
>
> if (cio_update_schib(sch)) {
> vfio_ccw_fsm_event(private, VFIO_CCW_EVENT_NOT_OPER);
> + rc = 0;
> goto out_unlock;
> }
>
> @@ -195,11 +197,12 @@ static int vfio_ccw_sch_event(struct subchannel *sch, int process)
> private->state = private->mdev ? VFIO_CCW_STATE_IDLE :
> VFIO_CCW_STATE_STANDBY;
> }
> + rc = 0;
>
> out_unlock:
> spin_unlock_irqrestore(sch->lock, flags);
>
> - return 0;
> + return rc;
> }
>
> static struct css_device_id vfio_ccw_sch_ids[] = {
Patch looks good to me.
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
I guess I should pick this for 4.17?
next prev parent reply other threads:[~2018-05-02 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 7:25 [PATCH 1/1] vfio: ccw: fix error return in vfio_ccw_sch_event Dong Jia Shi
2018-05-02 14:42 ` Cornelia Huck [this message]
[not found] ` <20180503020640.GW5428@bjsdjshi@linux.vnet.ibm.com>
2018-05-16 16:17 ` Cornelia Huck
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=20180502164251.577e2af8.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=bjsdjshi@linux.ibm.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=pmorel@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