public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v10 2/3] x86: correct usage of CFLAGS_NON_EFI
Date: Tue, 20 Apr 2021 10:21:57 -0400	[thread overview]
Message-ID: <20210420142157.GQ1310@bill-the-cat> (raw)
In-Reply-To: <20210411092158.5244-3-xypron.glpk@gmx.de>

On Sun, Apr 11, 2021 at 11:21:57AM +0200, Heinrich Schuchardt wrote:

> The current usage of the variable CFLAGS_NON_EFI on the x86 architecture
> deviates from other architectures.
> 
> Variable CFLAGS_NON_EFI is the list of compiler flags to be removed when
> building UEFI applications. It is not a list of flags to be added anywhere.
> 
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210420/6a7f5cc0/attachment.sig>

  parent reply	other threads:[~2021-04-20 14:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-11  9:21 [PATCH v10 0/3] Add support for stack-protector Heinrich Schuchardt
2021-04-11  9:21 ` [PATCH v10 1/3] test: fix test/dm/regmap.c Heinrich Schuchardt
2021-04-14 19:38   ` Simon Glass
2021-04-20 14:21   ` Tom Rini
2021-04-11  9:21 ` [PATCH v10 2/3] x86: correct usage of CFLAGS_NON_EFI Heinrich Schuchardt
2021-04-14 19:38   ` Simon Glass
2021-04-20 14:21   ` Tom Rini [this message]
2021-04-11  9:21 ` [PATCH v10 3/3] Add support for stack-protector Heinrich Schuchardt
2021-04-20 14:22   ` Tom Rini

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=20210420142157.GQ1310@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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