From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Anastasios Papagiannis <tasos.papagiannnis@gmail.com>
Cc: akpm@linux-foundation.org, bpf@vger.kernel.org,
liam@infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm/nommu: Reject wrapping ranges in access_remote_vm()
Date: Mon, 28 Sep 2026 16:07:44 +0100 [thread overview]
Message-ID: <arqCtS_MB2Ee3-44@gremlin> (raw)
In-Reply-To: <20260928150446.36873-1-tasos.papagiannnis@gmail.com>
On Mon, Sep 28, 2026 at 05:04:46PM +0200, Anastasios Papagiannis wrote:
> > BTW always feel free to nag if you're not getting review! Something things
> > get missed. (Though I'd say wait at least a couple weeks before doing
> > that!)
>
> Thanks! To be honest, it wasn't clear to me that I should take any futher action
> after I received an email that this patch was added to mm-new. But after reading
> that email again, this seems to be the case. The patch is still open for reviews.
> (Sorry, still learning how the process works..)
>
> [...]
>
> > Seems reasonable to me! So:
>
> > Reviewed-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
>
> Should I now send a v2 with those changes? It seems that these are already applied
> in https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/?id=1b721712d07e831686de53efc667561985897956.
No need, Andrew['s scripts] already fixed up thanks! :)
>
> Thanks,
> Anastasios
--
Cheers, Lorenzo
prev parent reply other threads:[~2026-09-28 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 6:42 Anastasios Papagiannis
2026-09-09 7:13 ` Andrew Morton
2026-09-09 20:11 ` Hajime Tazaki
2026-09-25 13:08 ` Lorenzo Stoakes (ARM)
2026-09-25 13:20 ` Lorenzo Stoakes (ARM)
2026-09-25 23:04 ` Andrew Morton
2026-09-28 15:04 ` Anastasios Papagiannis
2026-09-28 15:07 ` Lorenzo Stoakes (ARM) [this message]
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=arqCtS_MB2Ee3-44@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tasos.papagiannnis@gmail.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
all inboxes | Powered by JetHome®