From: Johannes Thumshirn <jthumshirn@suse.de>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
dan.j.williams@intel.com, mpe@ellerman.id.au, oohall@gmail.com
Cc: Sachin Sant <sachinp@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-nvdimm@lists.01.org
Subject: Re: [PATCH 1/2] libnvdimm/altmap: Track namespace boundaries in altmap
Date: Wed, 11 Sep 2019 14:03:44 +0200 [thread overview]
Message-ID: <26b12cb9-3062-2769-74f4-c5fce70d45a7@suse.de> (raw)
In-Reply-To: <20190910062826.10041-1-aneesh.kumar@linux.ibm.com>
Looks good,
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn@suse.de +49 911 74053 689
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nürnberg
Germany
(HRB 247165, AG München)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2019-09-11 12:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 6:28 [PATCH 1/2] libnvdimm/altmap: Track namespace boundaries in altmap Aneesh Kumar K.V
2019-09-10 6:28 ` [PATCH 2/2] powerpc/nvdimm: Update vmemmap_populated to check sub-section range Aneesh Kumar K.V
2019-09-16 17:46 ` Dan Williams
2019-09-17 9:54 ` Aneesh Kumar K.V
2019-09-17 5:47 ` Oliver O'Halloran
2019-09-10 7:40 ` [PATCH 1/2] libnvdimm/altmap: Track namespace boundaries in altmap Pankaj Gupta
2019-09-10 8:10 ` Dan Williams
2019-09-10 8:30 ` Aneesh Kumar K.V
2019-09-10 9:08 ` Dan Williams
2019-09-10 8:29 ` Santosh Sivaraj
2019-09-11 12:03 ` Johannes Thumshirn [this message]
2019-09-16 17:58 ` Dan Williams
2019-09-17 7:39 ` Aneesh Kumar K.V
2019-09-17 14:24 ` Dan Williams
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=26b12cb9-3062-2769-74f4-c5fce70d45a7@suse.de \
--to=jthumshirn@suse.de \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=linux-nvdimm@lists.01.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oohall@gmail.com \
--cc=sachinp@linux.vnet.ibm.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 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).