All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH/LOCAL 3/5] arm64: renesas: defconfig: Enable CONFIG_ARM64_RAS_EXTN
Date: Thu, 16 Dec 2021 16:43:54 +0100	[thread overview]
Message-ID: <da7cd1515f32dc3e9a52560fcdd8f161a475bd1e.1639669217.git.geert+renesas@glider.be> (raw)
In-Reply-To: <cover.1639669217.git.geert+renesas@glider.be>

Cortex-A55 (R-Car S4 and RZ/G2L) and Cortex-A76 (R-Car V3U) have RAS CPU
Extensions.

Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
 arch/arm64/configs/renesas_defconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/arch/arm64/configs/renesas_defconfig b/arch/arm64/configs/renesas_defconfig
index 805a14ca041ecbdc..6488805e418f3414 100644
--- a/arch/arm64/configs/renesas_defconfig
+++ b/arch/arm64/configs/renesas_defconfig
@@ -53,7 +53,6 @@ CONFIG_CRASH_DUMP=y
 CONFIG_XEN=y
 CONFIG_COMPAT=y
 # CONFIG_ARM64_USE_LSE_ATOMICS is not set
-# CONFIG_ARM64_RAS_EXTN is not set
 # CONFIG_ARM64_PTR_AUTH is not set
 # CONFIG_ARM64_AMU_EXTN is not set
 # CONFIG_ARM64_TLB_RANGE is not set
-- 
2.25.1


  parent reply	other threads:[~2021-12-16 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 15:43 [PATCH/LOCAL 0/5] arm64: renesas: defconfig: Refresh for v5.16-rc1 and misc updates Geert Uytterhoeven
2021-12-16 15:43 ` [PATCH/LOCAL 1/5] arm64: renesas: defconfig: Refresh for v5.16-rc1 Geert Uytterhoeven
2021-12-16 15:43 ` [PATCH/LOCAL 2/5] arm64: renesas: defconfig: Errata update Geert Uytterhoeven
2021-12-16 15:43 ` Geert Uytterhoeven [this message]
2021-12-16 15:43 ` [PATCH/LOCAL 4/5] arm64: renesas: defconfig: Enable CONFIG_SPI_RSPI Geert Uytterhoeven
2021-12-16 15:43 ` [PATCH/LOCAL 5/5] arm64: renesas: defconfig: Enable R8A779F0 SoC Geert Uytterhoeven

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=da7cd1515f32dc3e9a52560fcdd8f161a475bd1e.1639669217.git.geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@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.