From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org, linux-cxl@vger.kernel.org,
linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Ben Widawsky <bwidawsk@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/3] cxl: documentation fixes
Date: Thu, 4 Aug 2022 14:54:45 +0700 [thread overview]
Message-ID: <20220804075448.98241-1-bagasdotme@gmail.com> (raw)
Building htmldocs on next-20220803 (for which this series is based on),
there are new warnings on cxl subsystem. The fixes below are
self-explanatory.
Bagas Sanjaya (3):
cxl/regions: add padding for cxl_rr_ep_add nested lists
cxl/region: describe targets and nr_targets members of
cxl_region_params
Documentation: cxl: remove dangling kernel-doc reference
Documentation/driver-api/cxl/memory-devices.rst | 3 ---
drivers/cxl/core/region.c | 3 +++
drivers/cxl/cxl.h | 2 ++
3 files changed, 5 insertions(+), 3 deletions(-)
base-commit: 861397378de91c64dec69a160595b891f443294f
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2022-08-04 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 7:54 Bagas Sanjaya [this message]
2022-08-04 7:54 ` [PATCH 1/3] cxl/regions: add padding for cxl_rr_ep_add nested lists Bagas Sanjaya
2022-08-04 9:15 ` Jonathan Cameron
2022-08-04 7:54 ` [PATCH 2/3] cxl/region: describe targets and nr_targets members of cxl_region_params Bagas Sanjaya
2022-08-04 13:35 ` Jonathan Cameron
2022-08-04 7:54 ` [PATCH 3/3] Documentation: cxl: remove dangling kernel-doc reference Bagas Sanjaya
2022-08-04 13:32 ` Jonathan Cameron
2022-08-05 0:48 ` [PATCH 0/3] cxl: documentation fixes Dan Williams
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=20220804075448.98241-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.