[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen staging] evtchn: ECS_CLOSED => ECS_FREE
commit d72d6153be68f45e8f1c1b9e025cbfa625bbef6d Author: Jan Beulich <jbeulich@xxxxxxxx> AuthorDate: Wed Sep 30 09:12:21 2020 +0200 Commit: Jan Beulich <jbeulich@xxxxxxxx> CommitDate: Wed Sep 30 09:12:21 2020 +0200 evtchn: ECS_CLOSED => ECS_FREE There's no ECS_CLOSED; correct a comment naming it. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Julien Grall <jgrall@xxxxxxxxxx> Reviewed-by: Paul Durrant <paul@xxxxxxx> --- xen/common/event_channel.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xen/common/event_channel.c b/xen/common/event_channel.c index 161cbb77d2..2412e63204 100644 --- a/xen/common/event_channel.c +++ b/xen/common/event_channel.c @@ -668,7 +668,7 @@ int evtchn_close(struct domain *d1, int port1, bool guest) * 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; -- generated by git-patchbot for /home/xen/git/xen.git#staging
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |