From: Conor Dooley <conor.dooley@microchip.com>
To: <linux-kernel@vger.kernel.org>
Cc: <mm-commits@vger.kernel.org>, <surenb@google.com>,
<willy@infradead.org>, <akpm@linux-foundation.org>
Subject: Re: + mm-drop-per-vma-lock-when-returning-vm_fault_retry-or-vm_fault_completed-fix.patch added to mm-unstable branch
Date: Wed, 26 Jul 2023 09:51:02 +0100 [thread overview]
Message-ID: <20230726-navy-eatery-76a68523906b@wendy> (raw)
In-Reply-To: <20230725173416.EFD4EC433C9@smtp.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]
On Tue, Jul 25, 2023 at 10:34:16AM -0700, Andrew Morton wrote:
>
> The patch titled
> Subject: mm-drop-per-vma-lock-when-returning-vm_fault_retry-or-vm_fault_completed-fix
> has been added to the -mm mm-unstable branch. Its filename is
> mm-drop-per-vma-lock-when-returning-vm_fault_retry-or-vm_fault_completed-fix.patch
>
> This patch will shortly appear at
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-drop-per-vma-lock-when-returning-vm_fault_retry-or-vm_fault_completed-fix.patch
>
> This patch will later appear in the mm-unstable branch at
> git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>
> Before you just go and hit "reply", please:
> a) Consider who else should be cc'ed
> b) Prefer to cc a suitable mailing list as well
> c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
>
> *** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
>
> The -mm tree is included into linux-next via the mm-everything
> branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> and is updated there every 2-3 working days
>
> ------------------------------------------------------
> From: Matthew Wilcox <willy@infradead.org>
> Subject: mm-drop-per-vma-lock-when-returning-vm_fault_retry-or-vm_fault_completed-fix
> Date: Tue, 25 Jul 2023 15:31:17 +0100
>
> fix riscv
>
> Link: https://lkml.kernel.org/r/CAJuCfpE6GWEx1rPBmNpUfoD5o-gNFz9-UFywzCE2PbEGBiVz7g@mail.gmail.com
> Signed-off-by: Matthew Wilcox <willy@infradead.org>
> Reported-by: Conor Dooley <conor.dooley@microchip.com>
> Closes: https://lkml.kernel.org/r/20230725-anaconda-that-ac3f79880af1@wendy
> Cc: Suren Baghdasaryan <surenb@google.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Things look good in today's next with this fix. Thanks.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
parent reply other threads:[~2023-07-26 8:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230725173416.EFD4EC433C9@smtp.kernel.org>]
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=20230726-navy-eatery-76a68523906b@wendy \
--to=conor.dooley@microchip.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=surenb@google.com \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®