From: "Weiny, Ira" <ira.weiny@intel.com>
To: luanshi <zhangliguang@linux.alibaba.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"Verma, Vishal L" <vishal.l.verma@intel.com>,
"Jiang, Dave" <dave.jiang@intel.com>,
"Busch, Keith" <keith.busch@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: RE: [PATCH] libnvdimm: fix kernel-doc notation
Date: Wed, 16 Oct 2019 16:20:09 +0000 [thread overview]
Message-ID: <2807E5FD2F6FDA4886F6618EAC48510E92B4C086@CRSMSX102.amr.corp.intel.com> (raw)
In-Reply-To: <1571192160-54202-1-git-send-email-zhangliguang@linux.alibaba.com>
> Fix kernel-doc notation in drivers/nvdimm/namespace_devs.c.
>
> Fixes: bf9bccc14c05 ("libnvdimm: pmem label sets and namespace
> instantiation.")
> Signed-off-by: Liguang Zhang <zhangliguang@linux.alibaba.com>
> ---
> drivers/nvdimm/namespace_devs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/nvdimm/namespace_devs.c
> b/drivers/nvdimm/namespace_devs.c index cca0a3b..5cfb1e9 100644
> --- a/drivers/nvdimm/namespace_devs.c
> +++ b/drivers/nvdimm/namespace_devs.c
> @@ -1900,7 +1900,7 @@ static int select_pmem_id(struct nd_region
> *nd_region, u8 *pmem_id)
> /**
> * create_namespace_pmem - validate interleave set labelling, retrieve
> label0
> * @nd_region: region with mappings to validate
> - * @nspm: target namespace to create
> + * @ndindex: target namespace index to create
nsindex? 's'?
Ira
> * @nd_label: target pmem namespace label to evaluate
> */
> static struct device *create_namespace_pmem(struct nd_region
> *nd_region,
> --
> 1.8.3.1
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
next prev parent reply other threads:[~2019-10-16 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 2:16 [PATCH] libnvdimm: fix kernel-doc notation luanshi
2019-10-16 16:20 ` Weiny, Ira [this message]
2019-10-17 1:20 ` 乱石
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=2807E5FD2F6FDA4886F6618EAC48510E92B4C086@CRSMSX102.amr.corp.intel.com \
--to=ira.weiny@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-nvdimm@lists.01.org \
--cc=vishal.l.verma@intel.com \
--cc=zhangliguang@linux.alibaba.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).