All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>, julien.grall@arm.com
Cc: xen-devel@lists.xensource.com, wei.liu2@citrix.com
Subject: Re: [PATCH v2] xen/arm: warn the user that we cannot route SPIs to Dom0 on ACPI
Date: Wed, 1 Jun 2016 15:49:09 +0100	[thread overview]
Message-ID: <574EF5E5.1020300@citrix.com> (raw)
In-Reply-To: <1464791931-29322-1-git-send-email-sstabellini@kernel.org>

On 01/06/16 15:38, Stefano Stabellini wrote:
> as a consequence of 9d77b3c01d1261ce17c10097a1b393f2893ca657 being
> reverted.
>
> Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>

Some style corrections.

> @@ -342,9 +344,22 @@ void vgic_enable_irqs(struct vcpu *v, uint32_t r, int n)
>      unsigned long flags;
>      int i = 0;
>      struct vcpu *v_target;
> +    struct domain *d = v->domain;
>  
>      while ( (i = find_next_bit(&mask, 32, i)) < 32 ) {
>          irq = i + (32 * n);
> +        /* Set the irq type and route it to guest only for SPI and Dom0 */
> +        if( irq_access_permitted(d, irq) && is_hardware_domain(d) &&

Space after if.

> +            ( irq >= 32 ) && ( !acpi_disabled ) )

Extraneous spaces, and pointless brackets for the acpi_disabled.

> +        {
> +            static int log_once = 0;

bool_t.  Also, missing a newline between the variable declaration and code.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      parent reply	other threads:[~2016-06-01 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-01 14:38 [PATCH v2] xen/arm: warn the user that we cannot route SPIs to Dom0 on ACPI Stefano Stabellini
2016-06-01 14:45 ` Julien Grall
2016-06-01 14:46   ` Wei Liu
2016-06-01 14:49 ` Andrew Cooper [this message]

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=574EF5E5.1020300@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=wei.liu2@citrix.com \
    --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.