From: Mark Rutland <mark.rutland@arm.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Julien Grall <julien.grall@arm.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
Ian Campbell <ijc@hellion.org.uk>,
xen-devel@lists.xenproject.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 4/4] Explicitly clean linux-system.axf and xen-system.axf
Date: Thu, 15 Dec 2016 11:50:01 +0000 [thread overview]
Message-ID: <20161215115000.GB21758@leverpostej> (raw)
In-Reply-To: <cb5e65ca-65a2-6e0c-47f5-1773d6173739@arm.com>
On Mon, Dec 12, 2016 at 02:50:20PM +0000, Andre Przywara wrote:
> Hi Konrad,
>
> On 12/12/16 14:47, Konrad Rzeszutek Wilk wrote:
> > On Tue, Nov 22, 2016 at 03:09:17PM +0000, Andre Przywara wrote:
> >> From: Christoffer Dall <christoffer.dall@linaro.org>
> >>
> >> When doing a make clean, only the output image currently configured to
> >> build is being removed. However, one would expect all build artifacts
> >> to be removed when doing a 'make clean' and when switching between Xen
> >> and Linux builds, it is easy to accidentally run an older build than
> >> intended. Simply hardcode the axf image file names.
> >>
> >> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
> >> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> >> Reviewed-by: Julien Grall <julien.grall@arm.com>
> >
> > Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> > Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>
> Thanks a lot!
>
> I will try to poke Mark to see if we can get this merged eventually.
I'm happy to take these so long as this doesn't adversely affect non-Xen
usage. I assume they don't. :)
Could you fix this up as per Julien's comments, and fold in the tags?
I'm happy to take that from a v3 or a git repo.
Thanks,
Mark.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-15 11:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 15:09 [PATCH v2 0/4] boot-wrapper: arm64: Xen support Andre Przywara
2016-11-22 15:09 ` [PATCH v2 1/4] Support for building in a Xen binary Andre Przywara
2016-12-12 14:46 ` Konrad Rzeszutek Wilk
2016-12-15 11:34 ` Julien Grall
2016-11-22 15:09 ` [PATCH v2 2/4] Xen: Support adding DT nodes Andre Przywara
2016-12-12 14:46 ` Konrad Rzeszutek Wilk
2016-12-15 11:41 ` Julien Grall
2016-11-22 15:09 ` [PATCH v2 3/4] Xen: Select correct dom0 console Andre Przywara
2016-11-22 15:09 ` [PATCH v2 4/4] Explicitly clean linux-system.axf and xen-system.axf Andre Przywara
2016-12-12 14:47 ` Konrad Rzeszutek Wilk
[not found] ` <20161212144729.GD1686@char.us.oracle.com>
2016-12-12 14:50 ` Andre Przywara
[not found] ` <cb5e65ca-65a2-6e0c-47f5-1773d6173739@arm.com>
2016-12-15 11:50 ` Mark Rutland [this message]
[not found] ` <20161122150917.16524-4-andre.przywara@arm.com>
2016-12-12 14:47 ` [PATCH v2 3/4] Xen: Select correct dom0 console Konrad Rzeszutek Wilk
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=20161215115000.GB21758@leverpostej \
--to=mark.rutland@arm.com \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=ijc@hellion.org.uk \
--cc=julien.grall@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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 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).