Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc1
Date: Fri, 16 Dec 2022 15:51:13 +0000	[thread overview]
Message-ID: <20221216155111.GA8949@willie-the-truck> (raw)

Hi Linus,

Please pull these two arm64 fixes for -rc1, fixing issues introduced by
the recent pull for 6.2. They're both straightforward: a Kconfig tweak
and a revert. Summary in the tag.

There are some other fixes kicking around, but they're not urgent at all
(things like benign sparse warnings) so I'll get back to them in the new
year.

Cheers,

Will

--->8

The following changes since commit 5f4c374760b031f06c69c2fdad1b0e981a1ad42f:

  Merge branch 'for-next/undef-traps' into for-next/core (2022-12-06 11:34:25 +0000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes

for you to fetch changes up to c0cd1d541704c45030cbb2031612fdd68e8e15d5:

  Revert "arm64: errata: Workaround possible Cortex-A715 [ESR|FAR]_ELx corruption" (2022-12-15 17:59:12 +0000)

----------------------------------------------------------------
arm64 fixes for -rc1

- Fix Kconfig dependencies to re-allow the enabling of function graph
  tracer and shadow call stacks at the same time.

- Revert the workaround for CPU erratum #2645198 since the CONFIG_
  guards were incorrect and the code has therefore not seen any real
  exposure in -next.

----------------------------------------------------------------
Ard Biesheuvel (1):
      ftrace: Allow WITH_ARGS flavour of graph tracer with shadow call stack

Will Deacon (1):
      Revert "arm64: errata: Workaround possible Cortex-A715 [ESR|FAR]_ELx corruption"

 Documentation/arm64/silicon-errata.rst |  2 --
 arch/Kconfig                           |  2 +-
 arch/arm64/Kconfig                     | 16 ----------------
 arch/arm64/include/asm/hugetlb.h       |  9 ---------
 arch/arm64/include/asm/pgtable.h       |  9 ---------
 arch/arm64/kernel/cpu_errata.c         |  7 -------
 arch/arm64/mm/hugetlbpage.c            | 21 ---------------------
 arch/arm64/mm/mmu.c                    | 21 ---------------------
 arch/arm64/tools/cpucaps               |  1 -
 9 files changed, 1 insertion(+), 87 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2022-12-16 15:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 15:51 Will Deacon [this message]
2022-12-16 19:50 ` [GIT PULL] arm64 fixes for -rc1 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-06-26 10:59 Will Deacon
2026-06-26 15:45 ` pr-tracker-bot
2026-02-20 15:41 Will Deacon
2026-02-20 20:50 ` pr-tracker-bot
2025-10-07  8:28 Will Deacon
2025-10-07 16:13 ` pr-tracker-bot
2025-06-05 13:41 Will Deacon
2025-06-05 18:53 ` pr-tracker-bot
2024-07-26  8:42 Will Deacon
2024-07-26 18:07 ` pr-tracker-bot
2024-05-23 10:20 Will Deacon
2024-05-23 19:28 ` pr-tracker-bot
2024-01-19 16:05 Will Deacon
2024-01-19 16:34 ` Rob Herring
2024-01-19 16:58   ` Rob Herring
2024-01-19 22:50 ` pr-tracker-bot
2023-09-08 15:30 Will Deacon
2023-09-08 20:00 ` pr-tracker-bot
2023-05-04 14:22 Will Deacon
2023-05-04 19:49 ` pr-tracker-bot
2021-11-10 18:52 Will Deacon
2021-11-10 20:09 ` pr-tracker-bot
2021-02-26 11:09 [GIT PULL] arm64: Fixes " Will Deacon
2021-02-26 18:31 ` pr-tracker-bot
2019-09-20 13:37 Will Deacon
2019-09-20 19:10 ` pr-tracker-bot
2019-01-04 18:24 [GIT PULL] arm64: fixes " Will Deacon
2019-01-05 20:20 ` pr-tracker-bot
2017-03-01  4:51 [GIT PULL] arm64 " Will Deacon
2016-08-05 15:48 [GIT PULL] arm64: " Will Deacon
2014-12-16 17:50 Will Deacon

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=20221216155111.GA8949@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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