From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bastian Blank <waldi@debian.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 1/3] xen: Control-flow cleanup
Date: Wed, 24 Mar 2010 10:53:13 -0700 [thread overview]
Message-ID: <4BAA5189.8080503@goop.org> (raw)
In-Reply-To: <20100324115137.GA10770@wavehammer.waldi.eu.org>
On 03/24/2010 04:51 AM, Bastian Blank wrote:
> It is nice to have only one return, but it does not make it easier to
> read or change.
>
Thanks, I agree, but I tweaked it to use "goto out" to preserve the
single return, and fixed some lines which can now be unwrapped with the
shallower indent.
J
> Signed-off-by: Bastian Blank<waldi@debian.org>
> ---
> arch/x86/xen/pci.c | 52 +++++++++++++++++++++++++++-------------------------
> 1 files changed, 27 insertions(+), 25 deletions(-)
>
> diff --git a/arch/x86/xen/pci.c b/arch/x86/xen/pci.c
> index 61e1ade..a83c74c 100644
> --- a/arch/x86/xen/pci.c
> +++ b/arch/x86/xen/pci.c
> @@ -42,32 +42,34 @@ int xen_register_gsi(u32 gsi, int triggering, int polarity)
>
> printk(KERN_DEBUG "xen: --> irq=%d\n", irq);
>
> - if (irq>= 0) {
> - setup_gsi.gsi = gsi;
> - setup_gsi.triggering = (triggering == ACPI_EDGE_SENSITIVE ?
> - 0 : 1);
> - setup_gsi.polarity = (polarity == ACPI_ACTIVE_HIGH ? 0 : 1);
> -
> - rc = HYPERVISOR_physdev_op(PHYSDEVOP_setup_gsi,&setup_gsi);
> - if (rc == -EEXIST)
> - printk(KERN_INFO "Already setup the GSI :%d\n", gsi);
> - else if (rc) {
> - printk(KERN_ERR "Failed to setup GSI :%d, err_code:%d\n",
> - gsi, rc);
> - BUG();
> - }
> + if (irq< 0)
> + return irq;
> +
> + setup_gsi.gsi = gsi;
> + setup_gsi.triggering = (triggering == ACPI_EDGE_SENSITIVE ?
> + 0 : 1);
> + setup_gsi.polarity = (polarity == ACPI_ACTIVE_HIGH ? 0 : 1);
> +
> + rc = HYPERVISOR_physdev_op(PHYSDEVOP_setup_gsi,&setup_gsi);
> + if (rc == -EEXIST)
> + printk(KERN_INFO "Already setup the GSI :%d\n", gsi);
> + else if (rc) {
> + printk(KERN_ERR "Failed to setup GSI :%d, err_code:%d\n",
> + gsi, rc);
> + BUG();
> + }
>
> - map_irq.domid = DOMID_SELF;
> - map_irq.type = MAP_PIRQ_TYPE_GSI;
> - map_irq.index = gsi;
> - map_irq.pirq = irq;
> + map_irq.domid = DOMID_SELF;
> + map_irq.type = MAP_PIRQ_TYPE_GSI;
> + map_irq.index = gsi;
> + map_irq.pirq = irq;
>
> - rc = HYPERVISOR_physdev_op(PHYSDEVOP_map_pirq,&map_irq);
> - if (rc) {
> - printk(KERN_WARNING "xen map irq failed %d\n", rc);
> - irq = -1;
> - }
> + rc = HYPERVISOR_physdev_op(PHYSDEVOP_map_pirq,&map_irq);
> + if (rc) {
> + printk(KERN_WARNING "xen map irq failed %d\n", rc);
> + return -1;
> }
> +
> return irq;
> }
>
>
next prev parent reply other threads:[~2010-03-24 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 11:51 [PATCH 1/3] xen: Control-flow cleanup Bastian Blank
2010-03-24 17:53 ` Jeremy Fitzhardinge [this message]
2010-03-24 22:51 ` Bastian Blank
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=4BAA5189.8080503@goop.org \
--to=jeremy@goop.org \
--cc=waldi@debian.org \
--cc=xen-devel@lists.xensource.com \
/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.