From: Dave Jiang <dave.jiang@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Dan Williams <djbw@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Ira Weiny <iweiny@kernel.org>,
nvdimm@lists.linux.dev
Subject: Re: [PATCH 1/2] libnvdimm: nd.h: clean up kernel-doc warnings
Date: Thu, 23 Jul 2026 14:09:35 -0700 [thread overview]
Message-ID: <85ab2829-f2d2-47f4-952b-e64c10e82d8a@intel.com> (raw)
In-Reply-To: <20260721172132.3718892-1-rdunlap@infradead.org>
On 7/21/26 10:21 AM, Randy Dunlap wrote:
> Add missing struct member, function parameters, and function return
> values to eliminate all kernel-doc warnings:
>
> Warning: include/linux/nd.h:124 struct member 'common' not described in 'nd_namespace_io'
> Warning: include/linux/nd.h:124 Excess struct member 'dev' description in 'nd_namespace_io'
> Warning: include/linux/nd.h:166 function parameter 'flags' not described in 'nvdimm_read_bytes'
> Warning: include/linux/nd.h:166 No description found for return value of 'nvdimm_read_bytes'
> Warning: include/linux/nd.h:185 function parameter 'flags' not described in 'nvdimm_write_bytes'
> Warning: include/linux/nd.h:185 No description found for return value of 'nvdimm_write_bytes'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Cc: Dan Williams <djbw@kernel.org>
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Cc: Dave Jiang <dave.jiang@intel.com>
> Cc: Alison Schofield <alison.schofield@intel.com>
> Cc: Ira Weiny <iweiny@kernel.org>
> Cc: nvdimm@lists.linux.dev
>
> include/linux/nd.h | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> --- linux-next-20260720.orig/include/linux/nd.h
> +++ linux-next-20260720/include/linux/nd.h
> @@ -110,7 +110,7 @@ static inline struct nd_namespace_common
>
> /**
> * struct nd_namespace_io - device representation of a persistent memory range
> - * @dev: namespace device created by the nd region driver
> + * @common: namespace device core infrastructure created by the nd region driver
> * @res: struct resource conversion of a NFIT SPA table
> * @size: cached resource_size(@res) for fast path size checks
> * @addr: virtual address to access the namespace range
> @@ -158,8 +158,11 @@ static inline struct nd_namespace_pmem *
> * @offset: namespace-relative starting offset
> * @buf: buffer to fill
> * @size: transfer length
> + * @flags: process (0) or atomic (1) context
> *
> * @buf is up-to-date upon return from this routine.
> + *
> + * Returns: %0 on success or a negative error code on failure
> */
> static inline int nvdimm_read_bytes(struct nd_namespace_common *ndns,
> resource_size_t offset, void *buf, size_t size,
> @@ -174,11 +177,14 @@ static inline int nvdimm_read_bytes(stru
> * @offset: namespace-relative starting offset
> * @buf: buffer to drain
> * @size: transfer length
> + * @flags: process (0) or atomic (1) context
> *
> * NVDIMM Namepaces disks do not implement sectors internally. Depending on
> * the @ndns, the contents of @buf may be in cpu cache, platform buffers,
> * or on backing memory media upon return from this routine. Flushing
> * to media is handled internal to the @ndns driver, if at all.
> + *
> + * Returns: %0 on success or a negative error code on failure
> */
> static inline int nvdimm_write_bytes(struct nd_namespace_common *ndns,
> resource_size_t offset, void *buf, size_t size,
next prev parent reply other threads:[~2026-07-23 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 17:21 Randy Dunlap
2026-07-21 17:21 ` [PATCH 2/2] nvdimm-btt: " Randy Dunlap
2026-07-23 21:09 ` Dave Jiang
2026-07-30 22:59 ` Alison Schofield
2026-07-23 21:09 ` Dave Jiang [this message]
2026-07-30 22:58 ` [PATCH 1/2] libnvdimm: nd.h: " Alison Schofield
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=85ab2829-f2d2-47f4-952b-e64c10e82d8a@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=djbw@kernel.org \
--cc=iweiny@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=rdunlap@infradead.org \
--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®