From: Andrew Morton <akpm@linux-foundation.org>
To: Charan Teja Kalla <charante@codeaurora.org>
Cc: vbabka@suse.cz, corbet@lwn.net, mcgrof@kernel.org,
keescook@chromium.org, yzaikin@google.com, osalvador@suse.de,
rientjes@google.com, mchehab+huawei@kernel.org,
lokeshgidra@google.com, andrew.a.klychkov@gmail.com,
xi.fengfei@h3c.com, nigupta@nvidia.com,
dave.hansen@linux.intel.com, famzheng@amazon.com,
mateusznosek0@gmail.com, oleksandr@redhat.com, sh_def@163.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
"vinmenon@codeaurora.org" <vinmenon@codeaurora.org>
Subject: Re: [PATCH V4,0/3] mm: compaction: proactive compaction trigger by user
Date: Thu, 15 Jul 2021 21:27:44 -0700 [thread overview]
Message-ID: <20210715212744.1a43012c21711bafd25e5b68@linux-foundation.org> (raw)
In-Reply-To: <c0150787-5f85-29ac-9666-05fabedabb1e@codeaurora.org>
On Sat, 3 Jul 2021 15:52:10 +0530 Charan Teja Kalla <charante@codeaurora.org> wrote:
> A gentle ping to have your valuable comments.
Can we please have a resend?
The series has two fixes against the current code. Please separate
that work out from the new feature. So a 2-patch series to fix the bugs
followed by a single patch to add your new feature.
next prev parent reply other threads:[~2021-07-16 4:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 15:18 [PATCH V4,0/3] mm: compaction: proactive compaction trigger by user Charan Teja Reddy
2021-06-18 15:18 ` [PATCH V4 1/3] mm: compaction: optimize proactive compaction deferrals Charan Teja Reddy
2021-06-18 15:18 ` [PATCH V4 2/3] mm: compaction: support triggering of proactive compaction by user Charan Teja Reddy
2021-06-18 15:18 ` [PATCH V4 3/3] mm: compaction: fix wakeup logic of proactive compaction Charan Teja Reddy
2021-07-03 10:22 ` [PATCH V4,0/3] mm: compaction: proactive compaction trigger by user Charan Teja Kalla
2021-07-16 4:27 ` Andrew Morton [this message]
2021-07-16 10:44 ` Charan Teja Kalla
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=20210715212744.1a43012c21711bafd25e5b68@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andrew.a.klychkov@gmail.com \
--cc=charante@codeaurora.org \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=famzheng@amazon.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=mateusznosek0@gmail.com \
--cc=mcgrof@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nigupta@nvidia.com \
--cc=oleksandr@redhat.com \
--cc=osalvador@suse.de \
--cc=rientjes@google.com \
--cc=sh_def@163.com \
--cc=vbabka@suse.cz \
--cc=vinmenon@codeaurora.org \
--cc=xi.fengfei@h3c.com \
--cc=yzaikin@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.