From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>
Cc: akpm@linux-foundation.org, david@kernel.org, riel@surriel.com,
Liam.Howlett@oracle.com, vbabka@suse.cz, harry.yoo@oracle.com,
jannh@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
syzbot+c27fa543e10a45d4e149@syzkaller.appspotmail.com
Subject: Re: [PATCH] mm/rmap: fix unlink_anon_vmas() handling of error case from anon_vma_fork
Date: Sun, 18 Jan 2026 12:31:47 +0000 [thread overview]
Message-ID: <026e2cd5-84fa-4f14-83cb-d6b49053b7ae@lucifer.local> (raw)
In-Reply-To: <CADhLXY5pgdUP_o+zZJ0mo+kN+PuFY8E1WDuxS=M0+tuhta2nzw@mail.gmail.com>
On Sun, Jan 18, 2026 at 05:54:35PM +0530, Deepanshu Kartikey wrote:
> Hi Lorenzo,
>
> Yes, I used AI for commit message drafting and to help
> articulate the technical explanation. The bug analysis, code fix,
> and testing are mine.
>
> I'll send v2 with proper acknowledgment. Thanks for catching this.
No, please don't - As I told you in the other reply, this patch is not
acceptable.
When a patch is not upstream the appropriate thing to do is to comment on
the series.
We rebase development patches before they go upstream, so it just makes no
sense.
In addition this patch is not upstreamble as-is. You are getting at the
issue, but you're effectively undermining what my series does with this
proposal.
So while I appreciate the report, unfortunately this is not a patch we can
do anything with.
>
> Deepanshu
Thanks, Lorenzo
prev parent reply other threads:[~2026-01-18 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 10:58 Deepanshu Kartikey
2026-01-18 11:45 ` Lorenzo Stoakes
2026-01-18 12:06 ` Lorenzo Stoakes
2026-01-18 12:24 ` Deepanshu Kartikey
2026-01-18 12:31 ` Lorenzo Stoakes [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=026e2cd5-84fa-4f14-83cb-d6b49053b7ae@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=harry.yoo@oracle.com \
--cc=jannh@google.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=syzbot+c27fa543e10a45d4e149@syzkaller.appspotmail.com \
--cc=vbabka@suse.cz \
/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