All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	Xen-devel <xen-devel@lists.xen.org>,
	Daniel De Graaf <dgdegra@tycho.nsa.gov>
Subject: Re: [PATCH] xsm/evtchn: Never pretend to have successfully created a Xen event channel
Date: Mon, 19 Jan 2015 11:41:33 +0000	[thread overview]
Message-ID: <54BCED6D.1040004@citrix.com> (raw)
In-Reply-To: <54BCFA970200007800056681@mail.emea.novell.com>

On 19/01/15 11:37, Jan Beulich wrote:
>>>> On 19.01.15 at 11:45, <andrew.cooper3@citrix.com> wrote:
>> --- a/xen/common/event_channel.c
>> +++ b/xen/common/event_channel.c
>> @@ -1155,21 +1155,25 @@ int alloc_unbound_xen_event_channel(
>>  
>>      spin_lock(&d->event_lock);
>>  
>> -    if ( (port = get_free_port(d)) < 0 )
>> +    rc = get_free_port(d);
>> +    if ( rc < 0 )
>>          goto out;
>> +    port = rc;
> While this is kind of unrelated to the real change done in this patch,
> I'm fine with it being here, but I wonder whether this shouldn't be
> accompanied by a type change of "port" (to evtchn_port_t).

There are a number of other places which could also do with similar
typechanges for port (evtchn_from_port(), port_is_valid() etc).  I would
suggest that any such change be a separate patch.

~Andrew

  reply	other threads:[~2015-01-19 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 10:45 [PATCH] xsm/evtchn: Never pretend to have successfully created a Xen event channel Andrew Cooper
2015-01-19 11:37 ` Jan Beulich
2015-01-19 11:41   ` Andrew Cooper [this message]
2015-01-19 12:17     ` Jan Beulich

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=54BCED6D.1040004@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    /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.