> -----Original Message----- > From: Xen-devel <xen-devel-boun...@lists.xenproject.org> On Behalf Of Jan > Beulich > Sent: 28 September 2020 12:00 > To: xen-devel@lists.xenproject.org > Cc: Andrew Cooper <andrew.coop...@citrix.com>; George Dunlap > <george.dun...@eu.citrix.com>; Ian > Jackson <i...@xenproject.org>; Julien Grall <jul...@xen.org>; Wei Liu > <w...@xen.org>; Stefano Stabellini > <sstabell...@kernel.org> > Subject: [PATCH 08/12] evtchn: ECS_CLOSED => ECS_FREE > > There's no ECS_CLOSED; correct a comment naming it. > > Signed-off-by: Jan Beulich <jbeul...@suse.com> >
Reviewed-by: Paul Durrant <p...@xen.org> > --- a/xen/common/event_channel.c > +++ b/xen/common/event_channel.c > @@ -673,7 +673,7 @@ int evtchn_close(struct domain *d1, int > * We can only get here if the port was closed and re-bound after > * unlocking d1 but before locking d2 above. We could retry but > * it is easier to return the same error as if we had seen the > - * port in ECS_CLOSED. It must have passed through that state for > + * port in ECS_FREE. It must have passed through that state for > * us to end up here, so it's a valid error to return. > */ > rc = -EINVAL; >
