From: Will Deacon <will.deacon@arm.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Joerg Roedel <jroedel@suse.de>,
Auger Eric <eric.auger@redhat.com>,
Wei Yongjun <weiyj.lk@gmail.com>,
Wei Yongjun <weiyongjun1@huawei.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH -next] vfio/type1: fix error return code in vfio_iommu_type1_attach_group()
Date: Fri, 10 Feb 2017 11:56:47 +0000 [thread overview]
Message-ID: <20170210115647.GC32547@arm.com> (raw)
In-Reply-To: <20170209112311.4d4616a9@t450s.home>
On Thu, Feb 09, 2017 at 11:23:11AM -0700, Alex Williamson wrote:
> On Thu, 9 Feb 2017 18:03:47 +0100
> Auger Eric <eric.auger@redhat.com> wrote:
> > On 09/02/2017 17:01, Wei Yongjun wrote:
> > > From: Wei Yongjun <weiyongjun1@huawei.com>
> > >
> > > Fix to return a negative error code from the error handling
> > > case instead of 0, as done elsewhere in this function.
> > >
> > > Fixes: 5d704992189f ("vfio/type1: Allow transparent MSI IOVA allocation")
> > > Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
> >
> > Reviewed-by: Eric Auger <eric.auger@redhat.com>
>
> Acked-by: Alex Williamson <alex.williamson@redhat.com>
>
> Joerg/Will,
>
> The original commit comes in through iommu/next (arm/core), please feel
> free to also include this fix. Thanks,
Patch looks fine to me. Joerg, can you pick this up please?
Will
next prev parent reply other threads:[~2017-02-10 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 16:01 [PATCH -next] vfio/type1: fix error return code in vfio_iommu_type1_attach_group() Wei Yongjun
2017-02-09 17:03 ` Auger Eric
2017-02-09 18:23 ` Alex Williamson
2017-02-10 11:56 ` Will Deacon [this message]
2017-02-10 12:51 ` Joerg Roedel
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=20170210115647.GC32547@arm.com \
--to=will.deacon@arm.com \
--cc=alex.williamson@redhat.com \
--cc=eric.auger@redhat.com \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=weiyj.lk@gmail.com \
--cc=weiyongjun1@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.