On Fri, 30 Jun 2017, Wei Chen wrote:
> It's a error message about XEN_DOMCTL_deassign_device, but the
> print message is XEN_DOMCTL_assign_device.
> 
> Signed-off-by: Wei Chen <wei.c...@arm.com>

Reviewed-by: Stefano Stabellini <sstabell...@kernel.org>


> ---
>  xen/drivers/passthrough/device_tree.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/xen/drivers/passthrough/device_tree.c 
> b/xen/drivers/passthrough/device_tree.c
> index a8f403a..92adea6 100644
> --- a/xen/drivers/passthrough/device_tree.c
> +++ b/xen/drivers/passthrough/device_tree.c
> @@ -209,8 +209,8 @@ int iommu_do_dt_domctl(struct xen_domctl *domctl, struct 
> domain *d,
>          ret = iommu_deassign_dt_device(d, dev);
>  
>          if ( ret )
> -            printk(XENLOG_G_ERR "XEN_DOMCTL_assign_dt_device: assign \"%s\""
> -                   " to dom%u failed (%d)\n",
> +            printk(XENLOG_G_ERR "XEN_DOMCTL_deassign_device: deassign \"%s\""
> +                   " from dom%u failed (%d)\n",
>                     dt_node_full_name(dev), d->domain_id, ret);
>          break;
>  
> -- 
> 2.7.4
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Reply via email to