public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io
Cc: quic_llindhol@quicinc.com, rebecca@quicinc.com,
	bob.c.feng@intel.com,  gaoliming@byosoft.com.cn
Subject: Re: [PATCH 0/4] BaseTools - various cleanups
Date: Mon, 9 Jan 2023 17:37:57 +0100	[thread overview]
Message-ID: <CAMj1kXF_e2TaEdqDhBuLt9iKWAu13Q2ZU-AWQnEpX2__d9kwqw@mail.gmail.com> (raw)
In-Reply-To: <20230105160503.1423627-1-ardb@kernel.org>

On Thu, 5 Jan 2023 at 17:05, Ard Biesheuvel <ardb@kernel.org> wrote:
>
> Some cleanups for the tools_def template, mostly related to ARM but with
> some CLANG38 and RISCV changes as well.
>

Bob, Liming: any concerns regarding this series?


> Ard Biesheuvel (4):
>   BaseTools/tools_def RISCV: Make OpenSBI references RISCV-only
>   BaseTools/tools_def ARM AARCH64: Get rid of ARCHCC and ARCHASM flags
>   BaseTools/tools_def ARM: Make choice for soft float ABI explicit
>   BaseTools/tools_def CLANG38: Suppress unaligned access warning
>
>  BaseTools/Conf/tools_def.template | 98 +++++++++-----------
>  1 file changed, 45 insertions(+), 53 deletions(-)
>
> --
> 2.39.0
>

  parent reply	other threads:[~2023-01-09 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 16:04 [PATCH 0/4] BaseTools - various cleanups Ard Biesheuvel
2023-01-05 16:05 ` [PATCH 1/4] BaseTools/tools_def RISCV: Make OpenSBI references RISCV-only Ard Biesheuvel
2023-01-05 16:09   ` Chang, Abner
2023-01-09  5:22     ` Sunil V L
2023-01-05 16:05 ` [PATCH 2/4] BaseTools/tools_def ARM AARCH64: Get rid of ARCHCC and ARCHASM flags Ard Biesheuvel
2023-01-05 16:05 ` [PATCH 3/4] BaseTools/tools_def ARM: Make choice for soft float ABI explicit Ard Biesheuvel
2023-01-05 16:05 ` [PATCH 4/4] BaseTools/tools_def CLANG38: Suppress unaligned access warning Ard Biesheuvel
2023-01-09 16:37 ` Ard Biesheuvel [this message]
2023-01-10 13:10   ` [PATCH 0/4] BaseTools - various cleanups 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=CAMj1kXF_e2TaEdqDhBuLt9iKWAu13Q2ZU-AWQnEpX2__d9kwqw@mail.gmail.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