All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 6.5-rc4
Date: Fri, 28 Jul 2023 16:50:50 +0100	[thread overview]
Message-ID: <ZMPj2vX57s2hrNqk@arm.com> (raw)

Hi Linus,

Please pull the arm64/ACPI fixes below. Thanks.

The following changes since commit d4d5be94a87872421ea2569044092535aff0b886:

  arm64/fpsimd: Ensure SME storage is allocated after SVE VL changes (2023-07-21 11:11:09 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 003e6b56d780095a9adc23efc9cb4b4b4717169b:

  ACPI/IORT: Remove erroneous id_count check in iort_node_get_rmr_info() (2023-07-28 14:50:50 +0100)

----------------------------------------------------------------
A couple of SME updates for recent fixes (one of which went to stable):
reverting the flushing of the SME hardware state along with the thread
flushing and making sure we have the correct vector length before
reallocating.

An ACPI/IORT fix to avoid skipping ID mappings whose "number of IDs" is
0 (the spec reports the number of IDs in the mapping range minus 1).

----------------------------------------------------------------
Guanghui Feng (1):
      ACPI/IORT: Remove erroneous id_count check in iort_node_get_rmr_info()

Mark Brown (2):
      arm64/fpsimd: Don't flush SME register hardware state along with thread
      arm64/sme: Set new vector length before reallocating

 arch/arm64/kernel/fpsimd.c | 5 ++---
 drivers/acpi/arm64/iort.c  | 3 ---
 2 files changed, 2 insertions(+), 6 deletions(-)

-- 
Catalin

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

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 6.5-rc4
Date: Fri, 28 Jul 2023 16:50:50 +0100	[thread overview]
Message-ID: <ZMPj2vX57s2hrNqk@arm.com> (raw)

Hi Linus,

Please pull the arm64/ACPI fixes below. Thanks.

The following changes since commit d4d5be94a87872421ea2569044092535aff0b886:

  arm64/fpsimd: Ensure SME storage is allocated after SVE VL changes (2023-07-21 11:11:09 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 003e6b56d780095a9adc23efc9cb4b4b4717169b:

  ACPI/IORT: Remove erroneous id_count check in iort_node_get_rmr_info() (2023-07-28 14:50:50 +0100)

----------------------------------------------------------------
A couple of SME updates for recent fixes (one of which went to stable):
reverting the flushing of the SME hardware state along with the thread
flushing and making sure we have the correct vector length before
reallocating.

An ACPI/IORT fix to avoid skipping ID mappings whose "number of IDs" is
0 (the spec reports the number of IDs in the mapping range minus 1).

----------------------------------------------------------------
Guanghui Feng (1):
      ACPI/IORT: Remove erroneous id_count check in iort_node_get_rmr_info()

Mark Brown (2):
      arm64/fpsimd: Don't flush SME register hardware state along with thread
      arm64/sme: Set new vector length before reallocating

 arch/arm64/kernel/fpsimd.c | 5 ++---
 drivers/acpi/arm64/iort.c  | 3 ---
 2 files changed, 2 insertions(+), 6 deletions(-)

-- 
Catalin

             reply	other threads:[~2023-07-28 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 15:50 Catalin Marinas [this message]
2023-07-28 15:50 ` [GIT PULL] arm64 fixes for 6.5-rc4 Catalin Marinas
2023-07-28 18:39 ` pr-tracker-bot
2023-07-28 18:39   ` pr-tracker-bot

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=ZMPj2vX57s2hrNqk@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@kernel.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 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.