From: David Woodhouse <dwmw2@infradead.org>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: "Liam R. Howlett" <Liam.Howlett@Oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vegard Nossum <vegard.nossum@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Fix error return in do_vmi_align_munmap()
Date: Thu, 29 Jun 2023 22:17:09 +0100 [thread overview]
Message-ID: <9a816818f4d0b3eadc1c16fa3f3d42225c55c4b1.camel@infradead.org> (raw)
In-Reply-To: <20230628131330.ufrp57vnfpynlapq@revolver>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
Hi Linus,
The following changes since commit 6aeadf7896bff4ca230702daba8788455e6b866e:
Merge tag 'docs-arm64-move' of git://git.lwn.net/linux (2023-06-27 21:52:15 -0700)
are available in the Git repository at:
git://git.infradead.org/users/dwmw2/linux unmap-fix-20230629
for you to fetch changes up to 6c26bd4384da24841bac4f067741bbca18b0fb74:
mm/mmap: Fix error return in do_vmi_align_munmap() (2023-06-28 14:39:07 +0100)
It's not *imperative* that this be a pull request instead of being
committed again through whatever tree wants to take it, but the commit
ID is already being referenced in the stable backports so ideally we'd
keep it the same.
----------------------------------------------------------------
David Woodhouse (1):
mm/mmap: Fix error return in do_vmi_align_munmap()
mm/mmap.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
next prev parent reply other threads:[~2023-06-29 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 10:42 [PATCH] mm/mmap: Fix error return in do_vmi_align_munmap() David Woodhouse
2023-06-28 10:52 ` Greg KH
2023-06-28 13:13 ` Liam R. Howlett
2023-06-29 21:17 ` David Woodhouse [this message]
2023-06-30 0:48 ` [GIT PULL] " 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=9a816818f4d0b3eadc1c16fa3f3d42225c55c4b1.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linuxfoundation.org \
--cc=vegard.nossum@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).