linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] more hotfixes for 6.4-rc1
Date: Sat, 6 May 2023 10:48:51 -0700	[thread overview]
Message-ID: <20230506104851.21c6a2846f208820e75e7559@linux-foundation.org> (raw)


Linus, please merge this batch of hotfixes, thanks.


The following changes since commit 418d5c98319f67b9ae651babea031b5394425c18:

  Merge tag 'devicetree-fixes-for-6.4-1' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux (2023-05-05 13:27:59 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2023-05-06-10-45

for you to fetch changes up to 58f5f6698a72a8af5d7bfc5f49b6df60f378f167:

  afs: fix the afs_dir_get_folio return value (2023-05-06 10:10:08 -0700)

----------------------------------------------------------------
Five hotfixes.  Three are cc:stable, two pertain to post-6.3 merge window
changes.

----------------------------------------------------------------
Christoph Hellwig (1):
      afs: fix the afs_dir_get_folio return value

Jan Kara (1):
      mm: do not reclaim private data from pinned page

Lorenzo Stoakes (1):
      mm/mmap/vma_merge: always check invariants

Ryusuke Konishi (2):
      nilfs2: fix infinite loop in nilfs_mdt_get_block()
      nilfs2: do not write dirty data after degenerating to read-only

 fs/afs/dir_edit.c   |  7 ++++---
 fs/nilfs2/bmap.c    | 16 ++++++++++++----
 fs/nilfs2/segment.c |  5 ++++-
 mm/mmap.c           | 10 +++++-----
 mm/vmscan.c         | 10 ++++++++++
 5 files changed, 35 insertions(+), 13 deletions(-)



             reply	other threads:[~2023-05-06 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 17:48 Andrew Morton [this message]
2023-05-06 18:54 ` 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=20230506104851.21c6a2846f208820e75e7559@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@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