public inbox for linux-kernel@vger.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>,
	regressions@leemhuis.info, manivannan.sadhasivam@linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fix/revert for 6.1
Date: Tue, 6 Dec 2022 17:57:21 +0000	[thread overview]
Message-ID: <Y4+CgaxbC0BVlE6h@arm.com> (raw)

Hi Linus,

Please pull the revert below. The qcom driver fix is being worked on but
not in time for 6.1, so revert the arm64 change that highlighted the
issue.

Thanks.

The following changes since commit 5b47348fc0b18a78c96f8474cc90b7525ad1bbfe:

  arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud (2022-11-18 19:31:54 +0000)

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 b7d9aae404841d9999b7476170867ae441e948d2:

  Revert "arm64: dma: Drop cache invalidation from arch_dma_prep_coherent()" (2022-12-06 17:30:39 +0000)

----------------------------------------------------------------
Revert the dropping of the cache invalidation from the arm64
arch_dma_prep_coherent() as it caused a regression in the qcom_q6v5_mss
remoteproc driver. The driver is already buggy but the original arm64
change made the problem obvious. The change will be re-introduced once
the driver is fixed.

----------------------------------------------------------------
Will Deacon (1):
      Revert "arm64: dma: Drop cache invalidation from arch_dma_prep_coherent()"

 arch/arm64/mm/dma-mapping.c | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

-- 
Catalin

             reply	other threads:[~2022-12-06 17:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 17:57 Catalin Marinas [this message]
2022-12-06 19:07 ` [GIT PULL] arm64 fix/revert for 6.1 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=Y4+CgaxbC0BVlE6h@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=regressions@leemhuis.info \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox