From: "Gao, Liming" <liming.gao@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 0/2] BaseTools ARM/AARCH64: improve XIP support
Date: Tue, 9 Aug 2016 04:01:26 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A1155E67DE@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1470652827-22986-1-git-send-email-ard.biesheuvel@linaro.org>
Reviewed-by: Liming Gao <liming.gao@intel.com>
> -----Original Message-----
> From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
> Sent: Monday, August 08, 2016 6:40 PM
> To: leif.lindholm@linaro.org; Zhu, Yonghong <yonghong.zhu@intel.com>;
> Gao, Liming <liming.gao@intel.com>; edk2-devel@lists.01.org
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Subject: [PATCH 0/2] BaseTools ARM/AARCH64: improve XIP support
>
> Patch #1 adds the missing XIP flags to CLANG35, to prevent code to be
> generated that performs unaligned accesses before the MMU is on.
>
> Patch #2 extends the XIP CC flags support to ARM.
>
> Ard Biesheuvel (2):
> BaseTools CLANG35: add missing XIP flags for AARCH64
> BaseTools ARM: impose strict alignment only for XIP modules
>
> BaseTools/Conf/build_rule.template | 2 +-
> BaseTools/Conf/tools_def.template | 21 ++++++++++++++++----
> 2 files changed, 18 insertions(+), 5 deletions(-)
>
> --
> 2.7.4
next prev parent reply other threads:[~2016-08-09 4:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 10:40 [PATCH 0/2] BaseTools ARM/AARCH64: improve XIP support Ard Biesheuvel
2016-08-08 10:40 ` [PATCH 1/2] BaseTools CLANG35: add missing XIP flags for AARCH64 Ard Biesheuvel
2016-08-08 10:40 ` [PATCH 2/2] BaseTools ARM: impose strict alignment only for XIP modules Ard Biesheuvel
2016-08-09 4:01 ` Gao, Liming [this message]
2016-08-09 7:53 ` [PATCH 0/2] BaseTools ARM/AARCH64: improve XIP support Ard Biesheuvel
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-list 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=4A89E2EF3DFEDB4C8BFDE51014F606A1155E67DE@shsmsx102.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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