xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Pawel Wieczorkiewicz <wipawel@amazon.de>, xen-devel@lists.xen.org
Cc: mpohlack@amazon.de, ross.lagerwall@citrix.com, konrad.wilk@oracle.com
Subject: Re: [livepatch-build-tools 4/4] livepatch-build: Handle newly created object files
Date: Mon, 29 Apr 2019 13:53:20 +0100	[thread overview]
Message-ID: <58c4bf01-f646-b14d-37f1-4300bb4099ee@citrix.com> (raw)
In-Reply-To: <20190408083224.104802-4-wipawel@amazon.de>

On 08/04/2019 09:32, Pawel Wieczorkiewicz wrote:
> Up to now the livepatch-build ignores newly created object files.
> When patch applies new .c file and augments its Makefile to build it
> the resulting object file is not taken into account for final linking
> step.
>
> Such newly created object files can be detected by comparing patched/
> and original/ directories and copied over to the output directory for
> the final linking step.
>
> Signed-off-by: Pawel Wieczorkiewicz <wipawel@amazon.de>
> Reviewed-by: Andra-Irina Paraschiv <andraprs@amazon.com>
> Reviewed-by: Bjoern Doebel <doebel@amazon.de>
> Reviewed-by: Norbert Manthey <nmanthey@amazon.de>

This looks to resolve:

https://xenproject.atlassian.net/browse/XEN-90

(I think?)

~Andrew

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

  reply	other threads:[~2019-04-29 12:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08  8:32 [livepatch-build-tools 1/4] livepatch-gcc: Allow toolchain command with versions Pawel Wieczorkiewicz
2019-04-08  8:32 ` [livepatch-build-tools 2/4] livepatch-gcc: Ignore built_in.o and prelink.o object files Pawel Wieczorkiewicz
2019-04-29 12:27   ` Ross Lagerwall
2019-04-08  8:32 ` [livepatch-build-tools 3/4] livepatch-build: Do not follow every symlink for patch file Pawel Wieczorkiewicz
2019-04-29 12:40   ` Ross Lagerwall
2019-04-29 15:24     ` Wieczorkiewicz, Pawel
2019-04-08  8:32 ` [livepatch-build-tools 4/4] livepatch-build: Handle newly created object files Pawel Wieczorkiewicz
2019-04-29 12:53   ` Andrew Cooper [this message]
2019-04-29 13:53     ` Ross Lagerwall
2019-04-29 13:53   ` Ross Lagerwall
2019-04-29 15:43     ` Wieczorkiewicz, Pawel
2019-04-29 12:27 ` [livepatch-build-tools 1/4] livepatch-gcc: Allow toolchain command with versions Ross Lagerwall

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=58c4bf01-f646-b14d-37f1-4300bb4099ee@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=mpohlack@amazon.de \
    --cc=ross.lagerwall@citrix.com \
    --cc=wipawel@amazon.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).