virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Mike Christie <michael.christie@oracle.com>,
	martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	target-devel@vger.kernel.org, mst@redhat.com,
	pbonzini@redhat.com, stefanha@redhat.com,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 04/17] vhost: prep vhost_dev_init users to handle failures
Date: Mon, 2 Nov 2020 13:57:02 +0800	[thread overview]
Message-ID: <0f4a5f72-01e7-46d1-f214-c61cbb812859@redhat.com> (raw)
In-Reply-To: <1603326903-27052-5-git-send-email-michael.christie@oracle.com>


On 2020/10/22 上午8:34, Mike Christie wrote:
> This is just a prep patch to get vhost_dev_init callers ready to handle
> the next patch where the function can fail. In this patch vhost_dev_init
> just returns 0, but I think it's easier to check for goto/error handling
> errors separated from the next patch.
>
> Signed-off-by: Mike Christie<michael.christie@oracle.com>
> ---
>   drivers/vhost/net.c   | 11 +++++++----
>   drivers/vhost/scsi.c  |  7 +++++--
>   drivers/vhost/test.c  |  9 +++++++--
>   drivers/vhost/vdpa.c  |  7 +++++--
>   drivers/vhost/vhost.c | 14 ++++++++------
>   drivers/vhost/vhost.h | 10 +++++-----
>   drivers/vhost/vsock.c |  9 ++++++---
>   7 files changed, 43 insertions(+), 24 deletions(-)


Acked-by: Jason Wang <jasowang@redhat.com>


_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  parent reply	other threads:[~2020-11-02  5:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1603326903-27052-1-git-send-email-michael.christie@oracle.com>
     [not found] ` <1603326903-27052-5-git-send-email-michael.christie@oracle.com>
2020-10-22  5:22   ` [PATCH 04/17] vhost: prep vhost_dev_init users to handle failures kernel test robot
2020-11-02  5:57   ` Jason Wang [this message]
2020-11-03 10:04   ` Dan Carpenter
     [not found] ` <1603326903-27052-2-git-send-email-michael.christie@oracle.com>
2020-10-26  3:33   ` [PATCH 01/17] vhost scsi: add lun parser helper Jason Wang
     [not found] ` <1603326903-27052-4-git-send-email-michael.christie@oracle.com>
2020-10-26  3:34   ` [PATCH 03/17] vhost net: use goto error handling in open Jason Wang
     [not found] ` <1603326903-27052-8-git-send-email-michael.christie@oracle.com>
2020-10-26  3:51   ` [PATCH 07/17] vhost scsi: support delayed IO vq creation Jason Wang
     [not found]     ` <49c2fc29-348c-06db-4823-392f7476d318@oracle.com>
2020-10-28  1:55       ` Jason Wang
2020-10-30  8:47       ` Michael S. Tsirkin
2020-11-02  6:36         ` Jason Wang
2020-11-02  6:49           ` Jason Wang
2020-10-29 21:47 ` [PATCH 00/17 V3] vhost: fix scsi cmd handling and cgroup support Michael S. Tsirkin
     [not found] ` <1603326903-27052-10-git-send-email-michael.christie@oracle.com>
2020-10-30  8:51   ` [PATCH 09/17] vhost scsi: fix cmd completion race Michael S. Tsirkin
2020-10-30 16:04     ` Paolo Bonzini

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=0f4a5f72-01e7-46d1-f214-c61cbb812859@redhat.com \
    --to=jasowang@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=michael.christie@oracle.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=target-devel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).