From: Michal Hocko <mhocko@kernel.org>
To: akpm@linux-foundation.org
Cc: vbabka@suse.cz, toshi.kani@hpe.com, rppt@linux.ibm.com,
richardw.yang@linux.intel.com, pasha.tatashin@soleen.com,
osalvador@suse.de, logang@deltatee.com, jmoyer@redhat.com,
jglisse@redhat.com, jgg@mellanox.com, jane.chu@oracle.com,
hch@lst.de, david@redhat.com, corbet@lwn.net, cai@lca.pw,
aneesh.kumar@linux.ibm.com, dan.j.williams@intel.com,
linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [patch 23/38] mm/sparsemem: introduce struct mem_section_usage
Date: Fri, 19 Jul 2019 08:13:13 +0200 [thread overview]
Message-ID: <20190719061313.GI30461@dhcp22.suse.cz> (raw)
In-Reply-To: <20190718225757.ndUBg%akpm@linux-foundation.org>
On Thu 18-07-19 15:57:57, Andrew Morton wrote:
> From: Dan Williams <dan.j.williams@intel.com>
> Subject: mm/sparsemem: introduce struct mem_section_usage
>
> Patch series "mm: Sub-section memory hotplug support", v10.
Has this been properly reviewed after the last rebase and is this
actually ready for merging? I have seen some follow up fixes
http://lkml.kernel.org/r/20190715081549.32577-1-osalvador@suse.de
and do not see those patches being in the pipe line. Or have they been
merged?
--
Michal Hocko
SUSE Labs
next parent reply other threads:[~2019-07-19 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190718225757.ndUBg%akpm@linux-foundation.org>
2019-07-19 6:13 ` Michal Hocko [this message]
2019-07-19 16:42 ` Linus Torvalds
2019-07-19 19:27 ` Dan Williams
2019-07-22 5:46 ` Michal Hocko
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=20190719061313.GI30461@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=cai@lca.pw \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=hch@lst.de \
--cc=jane.chu@oracle.com \
--cc=jgg@mellanox.com \
--cc=jglisse@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mm-commits@vger.kernel.org \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=richardw.yang@linux.intel.com \
--cc=rppt@linux.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=toshi.kani@hpe.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
all inboxes | Powered by JetHome®