All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Artem Mygaiev <artem_mygaiev@epam.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Julien Grall <julien.grall@arm.com>,
	wei.liu2@citrix.com
Subject: Re: [PATCH] xen/arm: Fix misplaced parentheses for PSCI version check
Date: Thu, 1 Dec 2016 02:06:56 +0000	[thread overview]
Message-ID: <20161201020656.GC11640@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1611301115390.2781@sstabellini-ThinkPad-X260>

On Wed, Nov 30, 2016 at 11:16:49AM -0800, Stefano Stabellini wrote:
> On Wed, 30 Nov 2016, Julien Grall wrote:
> > Hi Artem,
> > 
> > On 30/11/16 13:53, Artem Mygaiev wrote:
> > > Fix misplaced parentheses for PSCI version check
> > > 
> > > Signed-off-by: Artem Mygaiev <artem_mygaiev@epam.com>
> > 
> > Can you please include the coverity ID:
> > 
> > Coverity-ID: 1381830
> > 
> > With that:
> > 
> > Reviewed-by: Julien Grall <julien.grall@arm.com>
> > 
> > This has been introduced by me in commit 2831f20 "xen/arm: Add support of PSCI
> > v1.0 for the host" in Xen 4.7. I am not sure whether we should backport it.
>  
> I think we should backport it.
> 
> Wei, can I have a release-ack or do you want to wait until after the
> release?

Please wait until after the release.

Wei.

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

  reply	other threads:[~2016-12-01  2:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 13:53 [PATCH] xen/arm: Fix misplaced parentheses for PSCI version check Artem Mygaiev
2016-11-30 15:55 ` Julien Grall
2016-11-30 19:16   ` Stefano Stabellini
2016-12-01  2:06     ` Wei Liu [this message]
2016-12-03  1:01       ` Stefano Stabellini
2016-12-06 13:57   ` Artem Mygaiev

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=20161201020656.GC11640@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=artem_mygaiev@epam.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.