All of lore.kernel.org
 help / color / mirror / Atom feed
From: pgowda <pgowda.cve@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: anuj.mittal@intel.com, rwmacleod@gmail.com,
	umesh.kalappa0@gmail.com, pgowda <pgowda.cve@gmail.com>
Subject: [hardknott][PATCH v2] Add ARM support for Neoverse N2 CPU
Date: Mon, 10 Jan 2022 02:38:47 -0800	[thread overview]
Message-ID: <20220110103847.5601-1-pgowda.cve@gmail.com> (raw)

This patch backports the Arm support for Neoverse N2 CPU.

Upstream-Status: Backport
[https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=d7e8411f6a333d4054894ad3b23f23415a525230]

Signed-off-by: pgowda <pgowda.cve@gmail.com>
---
 meta/recipes-devtools/gcc/gcc-10.2.inc                           | 1 +
 ...verse-n2-support.patch => 0038-arm-neoverse-n2-support.patch} | 0
 2 files changed, 1 insertion(+)
 rename meta/recipes-devtools/gcc/gcc/{0038-aarch64-neoverse-n2-support.patch => 0038-arm-neoverse-n2-support.patch} (100%)

diff --git a/meta/recipes-devtools/gcc/gcc-10.2.inc b/meta/recipes-devtools/gcc/gcc-10.2.inc
index 656c43258c..e7e3395c55 100644
--- a/meta/recipes-devtools/gcc/gcc-10.2.inc
+++ b/meta/recipes-devtools/gcc/gcc-10.2.inc
@@ -74,6 +74,7 @@ SRC_URI = "\
            file://0002-CVE-2021-35465.patch \
            file://0003-CVE-2021-35465.patch \
            file://0004-CVE-2021-35465.patch \
+           file://0038-arm-neoverse-n2-support.patch \
            file://0039-arm64-neoverse-n2-support.patch \
            file://0001-CVE-2021-42574.patch \
            file://0002-CVE-2021-42574.patch \
diff --git a/meta/recipes-devtools/gcc/gcc/0038-aarch64-neoverse-n2-support.patch b/meta/recipes-devtools/gcc/gcc/0038-arm-neoverse-n2-support.patch
similarity index 100%
rename from meta/recipes-devtools/gcc/gcc/0038-aarch64-neoverse-n2-support.patch
rename to meta/recipes-devtools/gcc/gcc/0038-arm-neoverse-n2-support.patch
-- 
2.31.1



                 reply	other threads:[~2022-01-10 10:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220110103847.5601-1-pgowda.cve@gmail.com \
    --to=pgowda.cve@gmail.com \
    --cc=anuj.mittal@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rwmacleod@gmail.com \
    --cc=umesh.kalappa0@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.