From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Markus Elfring <Markus.Elfring@web.de>, <linux-nvdimm@lists.01.org>
Cc: <linux-kernel@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
"Oliver O'Halloran" <oohall@gmail.com>,
Vishal Verma <vishal.l.verma@intel.com>
Subject: Re: [PATCH v2 3/4] libnvdimm/bus: simplify walk_to_nvdimm_bus()
Date: Wed, 19 Aug 2020 21:35:20 +0800 [thread overview]
Message-ID: <ee3b1538-b19f-5dd9-d023-90eca4bfd9b7@huawei.com> (raw)
In-Reply-To: <ff1333cb-9917-6a2c-4454-325d161d8650@web.de>
On 8/19/2020 8:40 PM, Markus Elfring wrote:
>> … when is_nvdimm_bus(dev) successed.
>
> I imagine that that an other wording will be more appropriate here.
OK, I will rewrite it.
>
> Regards,
> Markus
>
>
next prev parent reply other threads:[~2020-08-19 13:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 2:04 [PATCH v2 0/4] bugfix and optimize for drivers/nvdimm Zhen Lei
2020-08-19 2:05 ` [PATCH v2 1/4] libnvdimm: fix memmory leaks in of_pmem.c Zhen Lei
[not found] ` <5cc26ce3-963e-3ab6-6f97-706cea00c5f3@web.de>
2020-08-19 13:34 ` [PATCH v2 1/4] libnvdimm: Fix memory " Leizhen (ThunderTown)
2020-08-19 13:35 ` Oliver O'Halloran
2020-08-19 14:18 ` Leizhen (ThunderTown)
2020-08-19 13:37 ` [PATCH v2 1/4] libnvdimm: fix memmory " Oliver O'Halloran
2020-08-19 14:19 ` Leizhen (ThunderTown)
2020-08-19 2:05 ` [PATCH v2 2/4] libnvdimm: add sanity check for provider_name in of_pmem_region_probe() Zhen Lei
2020-08-19 2:05 ` [PATCH v2 3/4] libnvdimm/bus: simplify walk_to_nvdimm_bus() Zhen Lei
[not found] ` <ff1333cb-9917-6a2c-4454-325d161d8650@web.de>
2020-08-19 13:35 ` Leizhen (ThunderTown) [this message]
2020-08-19 2:05 ` [PATCH v2 4/4] libnvdimm/region: reduce an unnecessary if branch in nd_region_create() Zhen Lei
[not found] ` <ce85d12b-f0bf-8cdd-0477-8ee87ff5a4c9@web.de>
2020-08-19 13:30 ` [PATCH v2 0/4] bug fix and optimize for drivers/nvdimm Leizhen (ThunderTown)
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=ee3b1538-b19f-5dd9-d023-90eca4bfd9b7@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=Markus.Elfring@web.de \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=oohall@gmail.com \
--cc=vishal.l.verma@intel.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
all inboxes | Powered by JetHome®