From: Alison Schofield <alison.schofield@intel.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Linux Documentation" <linux-doc@vger.kernel.org>,
Linux NVDIMM <nvdimm@lists.linux.dev>,
Dan Williams <dan.j.williams@intel.com>,
"Vishal Verma" <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
"Ira Weiny" <ira.weiny@intel.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: btt: Unwrap bit 31-30 nested table
Date: Wed, 5 Nov 2025 14:23:22 -0800 [thread overview]
Message-ID: <aQvOWuf5Wj7UTKKh@aschofie-mobl2.lan> (raw)
In-Reply-To: <20251105124707.44736-2-bagasdotme@gmail.com>
On Wed, Nov 05, 2025 at 07:47:08PM +0700, Bagas Sanjaya wrote:
> Bit 31-30 usage table is already formatted as reST simple table, but it
> is wrapped in literal code block instead. Unwrap it.
>
Reviewed-by: Alison Schofield <alison.schofield@intel.com>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Documentation/driver-api/nvdimm/btt.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/driver-api/nvdimm/btt.rst b/Documentation/driver-api/nvdimm/btt.rst
> index 107395c042ae07..2d8269f834bd60 100644
> --- a/Documentation/driver-api/nvdimm/btt.rst
> +++ b/Documentation/driver-api/nvdimm/btt.rst
> @@ -83,7 +83,7 @@ flags, and the remaining form the internal block number.
> ======== =============================================================
> Bit Description
> ======== =============================================================
> -31 - 30 Error and Zero flags - Used in the following way::
> +31 - 30 Error and Zero flags - Used in the following way:
>
> == == ====================================================
> 31 30 Description
>
> base-commit: 27600b51fbc8b9a4eba18c8d88d7edb146605f3f
> --
> An old man doll... just what I always wanted! - Clara
>
>
next prev parent reply other threads:[~2025-11-05 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 12:47 Bagas Sanjaya
2025-11-05 22:23 ` Alison Schofield [this message]
2025-11-06 5:13 ` Randy Dunlap
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=aQvOWuf5Wj7UTKKh@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--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®