All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Lagerwall <ross.lagerwall@citrix.com>
To: Pawel Wieczorkiewicz <wipawel@amazon.de>,
	<xen-devel@lists.xen.org>, <xen-devel@lists.xenproject.org>
Cc: wipawel@amazon.com, Stefano Stabellini <sstabellini@kernel.org>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
	Julien Grall <julien.grall@arm.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] [PATCH] livepatch: always print XENLOG_ERR information (ARM, ELF)
Date: Fri, 13 Sep 2019 11:01:53 +0100	[thread overview]
Message-ID: <104d5651-e054-ae62-3137-0a8e22429969@citrix.com> (raw)
In-Reply-To: <20190821100430.89909-1-wipawel@amazon.de>

On 8/21/19 11:04 AM, Pawel Wieczorkiewicz wrote:
> This complements [1] commit for ARM and livepatch_elf files.
> 
> [1] 4470efeae4 livepatch: always print XENLOG_ERR information
> 
> Signed-off-by: Pawel Wieczorkiewicz <wipawel@amazon.de>
> ---
>   xen/arch/arm/arm32/livepatch.c |  28 +++++------
>   xen/arch/arm/arm64/livepatch.c |  28 +++++------
>   xen/common/livepatch_elf.c     | 104 ++++++++++++++++++++---------------------
>   3 files changed, 80 insertions(+), 80 deletions(-)
> 
With Andrew's suggested whitespace changes:

Reviewed-by: Ross Lagerwall <ross.lagerwall@citrix.com>

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

      parent reply	other threads:[~2019-09-13 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21 10:04 [Xen-devel] [PATCH] livepatch: always print XENLOG_ERR information (ARM, ELF) Pawel Wieczorkiewicz
2019-08-21 10:20 ` Andrew Cooper
2019-08-21 21:16   ` Julien Grall
2019-09-13 10:01 ` Ross Lagerwall [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=104d5651-e054-ae62-3137-0a8e22429969@citrix.com \
    --to=ross.lagerwall@citrix.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=sstabellini@kernel.org \
    --cc=wipawel@amazon.com \
    --cc=wipawel@amazon.de \
    --cc=xen-devel@lists.xen.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.