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 2/2] nvdimm-btt: clean up kernel-doc warnings
Date: Thu, 23 Jul 2026 14:09:55 -0700 [thread overview]
Message-ID: <7cae90ce-832b-4262-bfb0-960f1ec69ac6@intel.com> (raw)
In-Reply-To: <20260721172132.3718892-2-rdunlap@infradead.org>
On 7/21/26 10:21 AM, Randy Dunlap wrote:
> Add one missing kernel-doc description and drop one that shouldn't be
> here in order to avoid kernel-doc warnings:
>
> Warning: ./drivers/nvdimm/btt.h:232 struct member 'nd_region' not described in 'btt'
> Warning: ./drivers/nvdimm/btt.h:232 Excess struct member 'lanes' description in 'btt'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Cc: Dan Williams <djbw@kernel.org>
> 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
>
> drivers/nvdimm/btt.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20260720.orig/drivers/nvdimm/btt.h
> +++ linux-next-20260720/drivers/nvdimm/btt.h
> @@ -210,7 +210,7 @@ struct badblocks;
> * @lbasize: LBA size as requested and presented to upper layers.
> * This is sector_size + size of any metadata.
> * @sector_size: The Linux sector size - 512 or 4096
> - * @lanes: Per-lane spinlocks
> + * @nd_region: &struct nd_region pointer
> * @init_lock: Mutex used for the BTT initialization
> * @init_state: Flag describing the initialization state for the BTT
> * @num_arenas: Number of arenas in the BTT instance
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 [PATCH 1/2] libnvdimm: nd.h: " Randy Dunlap
2026-07-21 17:21 ` [PATCH 2/2] nvdimm-btt: " Randy Dunlap
2026-07-23 21:09 ` Dave Jiang [this message]
2026-07-30 22:59 ` Alison Schofield
2026-07-23 21:09 ` [PATCH 1/2] libnvdimm: nd.h: " Dave Jiang
2026-07-30 22:58 ` 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=7cae90ce-832b-4262-bfb0-960f1ec69ac6@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®