Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: deepakroag <gaikwad.dcg@gmail.com>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] feat: scale vmpressure window with machine size
Date: Thu, 16 Jul 2026 19:19:38 +0530	[thread overview]
Message-ID: <20260716134938.42495-1-gaikwad.dcg@gmail.com> (raw)
In-Reply-To: <aljYxLusTzZkTfnH@lucifer>

Hi Lorenzo,

Thank you for the review. I withdraw the entire [PATCH v2 0/3] series.

You are right that the vmpressure change closely follows Benjamin Lee
McQueen's earlier rejected thread without proper attribution or an RFC.
That was a serious mistake on my part, and I am sorry for the confusion
and for wasting your time.

I will not resubmit the vmpressure or vrealloc changes. I also
understand that bundling unrelated mm, selftest, and vmalloc work in one
series, using non-kernel subject prefixes, and sending v2 without a
proper v1 review cycle were process errors on my side.

Going forward I will stick to small, original fixes, search lore before
proposing mm changes, and follow the normal RFC/review process for
anything touching vmpressure or vmalloc.

Thank you,
Deepak Rao Gaikwad


  reply	other threads:[~2026-07-16 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260716115734.80909-1-gaikwad.dcg@gmail.com>
2026-07-16 11:57 ` [PATCH v2 1/3] feat: scale vmpressure window with machine size deepakroag
2026-07-16 13:24   ` Lorenzo Stoakes (ARM)
2026-07-16 13:49     ` deepakroag [this message]
2026-07-16 11:57 ` [PATCH v2 3/3] feat: grow vrealloc vm_area mappings in place deepakroag

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=20260716134938.42495-1-gaikwad.dcg@gmail.com \
    --to=gaikwad.dcg@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.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