From: Juergen Gross <jgross@suse.com>
To: Souptick Joarder <jrdr.linux@gmail.com>,
richard.weiyang@gmail.com, dan.j.williams@intel.com,
sashal@kernel.org, sstabellini@kernel.org, cai@lca.pw,
akpm@linux-foundation.org, haiyangz@microsoft.com,
kys@microsoft.com, sthemmin@microsoft.com,
boris.ostrovsky@oracle.com, david@redhat.com,
pasha.tatashin@soleen.com, Michal Hocko <mhocko@suse.com>,
Oscar Salvador <osalvador@suse.com>
Cc: linux-mm@kvack.org, xen-devel@lists.xenproject.org,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] xen/ballon: Avoid calling dummy function __online_page_set_limits()
Date: Sun, 8 Sep 2019 07:09:32 +0200 [thread overview]
Message-ID: <6b666a74-da96-878a-9288-e0271428c0ee@suse.com> (raw)
In-Reply-To: <854db2cf8145d9635249c95584d9a91fd774a229.1567889743.git.jrdr.linux@gmail.com>
On 07.09.19 23:47, Souptick Joarder wrote:
> __online_page_set_limits() is a dummy function and an extra call
> to this function can be avoided.
>
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
next prev parent reply other threads:[~2019-09-08 5:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 21:47 [PATCH 0/3] Remove __online_page_set_limits() Souptick Joarder
2019-09-07 21:47 ` [PATCH 1/3] hv_ballon: Avoid calling dummy function __online_page_set_limits() Souptick Joarder
2019-09-09 7:54 ` David Hildenbrand
2019-09-07 21:47 ` [PATCH 2/3] xen/ballon: " Souptick Joarder
2019-09-08 5:09 ` Juergen Gross [this message]
2019-09-09 7:54 ` David Hildenbrand
2019-09-07 21:47 ` [PATCH 3/3] mm/memory_hotplug.c: Remove __online_page_set_limits() Souptick Joarder
2019-09-09 7:54 ` David Hildenbrand
2019-09-09 8:12 ` [PATCH 0/3] " Michal Hocko
2019-09-09 15:42 ` Kirill A. Shutemov
2019-09-10 12:56 ` Souptick Joarder
2019-09-10 12:58 ` David Hildenbrand
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=6b666a74-da96-878a-9288-e0271428c0ee@suse.com \
--to=jgross@suse.com \
--cc=akpm@linux-foundation.org \
--cc=boris.ostrovsky@oracle.com \
--cc=cai@lca.pw \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=haiyangz@microsoft.com \
--cc=jrdr.linux@gmail.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.com \
--cc=pasha.tatashin@soleen.com \
--cc=richard.weiyang@gmail.com \
--cc=sashal@kernel.org \
--cc=sstabellini@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).