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 5.19-rc5
Date: Fri, 1 Jul 2022 18:33:41 +0100	[thread overview]
Message-ID: <Yr8v9alP3O4HZudw@arm.com> (raw)

Hi Linus,

Please pull the arm64 fix below. Thanks.

The following changes since commit c50f11c6196f45c92ca48b16a5071615d4ae0572:

  arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer (2022-06-17 19:06:06 +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 410982303772993a86bb7a9cfa7ece34522b2636:

  arm64: hugetlb: Restore TLB invalidation for BBM on contiguous ptes (2022-07-01 18:29:26 +0100)

----------------------------------------------------------------
arm64 fix: restore TLB invalidation for the 'break-before-make' rule on
contiguous ptes (missed in a recent clean-up).

----------------------------------------------------------------
Will Deacon (1):
      arm64: hugetlb: Restore TLB invalidation for BBM on contiguous ptes

 arch/arm64/mm/hugetlbpage.c | 30 +++++++++++++++++++++---------
 1 file changed, 21 insertions(+), 9 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 5.19-rc5
Date: Fri, 1 Jul 2022 18:33:41 +0100	[thread overview]
Message-ID: <Yr8v9alP3O4HZudw@arm.com> (raw)

Hi Linus,

Please pull the arm64 fix below. Thanks.

The following changes since commit c50f11c6196f45c92ca48b16a5071615d4ae0572:

  arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer (2022-06-17 19:06:06 +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 410982303772993a86bb7a9cfa7ece34522b2636:

  arm64: hugetlb: Restore TLB invalidation for BBM on contiguous ptes (2022-07-01 18:29:26 +0100)

----------------------------------------------------------------
arm64 fix: restore TLB invalidation for the 'break-before-make' rule on
contiguous ptes (missed in a recent clean-up).

----------------------------------------------------------------
Will Deacon (1):
      arm64: hugetlb: Restore TLB invalidation for BBM on contiguous ptes

 arch/arm64/mm/hugetlbpage.c | 30 +++++++++++++++++++++---------
 1 file changed, 21 insertions(+), 9 deletions(-)

-- 
Catalin

             reply	other threads:[~2022-07-01 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 17:33 Catalin Marinas [this message]
2022-07-01 17:33 ` [GIT PULL] arm64 fixes for 5.19-rc5 Catalin Marinas
2022-07-01 18:27 ` pr-tracker-bot
2022-07-01 18:27   ` 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=Yr8v9alP3O4HZudw@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.