ject.org; linux-ker...@vger.kernel.org;
> Juergen
> >> Gross ; Stefano Stabellini ;
> >> Boris Ostrovsky
> >> Subject: Re: [Xen-devel] [PATCH v2 2/4] xenbus: limit when state is
> forced
> >> to closed
> >>
> >> On Tue, Dec 10, 2019 at
] xenbus: limit when state is forced
to closed
On Tue, Dec 10, 2019 at 11:33:45AM +, Paul Durrant wrote:
If a driver probe() fails then leave the xenstore state alone. There is
no
reason to modify it as the failure may be due to transient resource
allocation issues and hence a subsequent
> -Original Message-
> From: Roger Pau Monné
> Sent: 11 December 2019 10:06
> To: Durrant, Paul
> Cc: xen-devel@lists.xenproject.org; linux-ker...@vger.kernel.org; Juergen
> Gross ; Stefano Stabellini ;
> Boris Ostrovsky
> Subject: Re: [Xen-devel] [PATCH v2 2/4]
On Tue, Dec 10, 2019 at 11:33:45AM +, Paul Durrant wrote:
> If a driver probe() fails then leave the xenstore state alone. There is no
> reason to modify it as the failure may be due to transient resource
> allocation issues and hence a subsequent probe() may succeed.
>
> If the driver support
If a driver probe() fails then leave the xenstore state alone. There is no
reason to modify it as the failure may be due to transient resource
allocation issues and hence a subsequent probe() may succeed.
If the driver supports re-binding then only force state to closed during
remove() only in the
