From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Cc: "Schofield, Alison" <alison.schofield@intel.com>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>
Subject: Re: [ndctl PATCH v2 07/18] cxl/list: Add parent_dport attribute to port listings
Date: Wed, 4 Jan 2023 20:15:53 +0000 [thread overview]
Message-ID: <b509af356cd2f18e3bf847d10e772a0ec701423a.camel@intel.com> (raw)
In-Reply-To: <639d1d3bc99a_b41e32948@dwillia2-xfh.jf.intel.com.notmuch>
On Fri, 2022-12-16 at 17:36 -0800, Dan Williams wrote:
> Dan Williams wrote:
> >
> > ---
> > cxl/json.c | 8 ++++++++
> > cxl/lib/libcxl.c | 38 ++++++++++++++++++++++++++++++++++++++
> > cxl/lib/libcxl.sym | 1 +
> > cxl/lib/private.h | 2 ++
> > cxl/libcxl.h | 1 +
> > 5 files changed, 50 insertions(+)
>
> I should not have sent this out. It was sitting in my development
> tree
> for other work, but should have been held back until the kernel
> support
> landed.
>
> Drop this for now as the kernel support will not arrive until v6.3:
>
> http://lore.kernel.org/r/167124082375.1626103.6047000000121298560.stgit@dwillia2-xfh.jf.intel.com
Ah it has made it out to pending already.. shall I just revert it?
next prev parent reply other threads:[~2023-01-04 20:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 21:27 [ndctl PATCH v2 00/18] cxl-cli test and usability updates Dan Williams
2022-12-08 21:28 ` [ndctl PATCH v2 01/18] ndctl/test: Move firmware-update.sh to the 'destructive' set Dan Williams
2022-12-09 17:13 ` Alison Schofield
2022-12-08 21:28 ` [ndctl PATCH v2 02/18] ndctl/test: Add kernel backtrace detection to some dax tests Dan Williams
2022-12-08 21:28 ` [ndctl PATCH v2 03/18] ndctl/clang-format: Move minimum version to 6 Dan Williams
2022-12-08 21:28 ` [ndctl PATCH v2 04/18] ndctl/clang-format: Fix space after for_each macros Dan Williams
2022-12-09 17:22 ` Alison Schofield
2022-12-12 18:16 ` Verma, Vishal L
2022-12-08 21:28 ` [ndctl PATCH v2 05/18] cxl/list: Always attempt to collect child objects Dan Williams
2022-12-08 21:28 ` [ndctl PATCH v2 06/18] cxl/list: Add a 'firmware_node' alias Dan Williams
2022-12-08 21:28 ` [ndctl PATCH v2 07/18] cxl/list: Add parent_dport attribute to port listings Dan Williams
2022-12-17 1:36 ` Dan Williams
2023-01-04 20:15 ` Verma, Vishal L [this message]
2022-12-08 21:28 ` [ndctl PATCH v2 08/18] cxl/list: Skip emitting pmem_size when it is zero Dan Williams
2022-12-09 17:26 ` Alison Schofield
2022-12-08 21:28 ` [ndctl PATCH v2 09/18] cxl/filter: Return json-c topology Dan Williams
2022-12-09 17:27 ` Alison Schofield
2022-12-08 21:28 ` [ndctl PATCH v2 10/18] cxl/list: Record cxl objects in json objects Dan Williams
2022-12-09 17:28 ` Alison Schofield
2022-12-08 21:29 ` [ndctl PATCH v2 11/18] cxl/region: Make ways an integer argument Dan Williams
2022-12-09 17:29 ` Alison Schofield
2022-12-08 21:29 ` [ndctl PATCH v2 12/18] cxl/region: Make granularity " Dan Williams
2022-12-09 17:30 ` Alison Schofield
2022-12-08 21:29 ` [ndctl PATCH v2 13/18] cxl/region: Use cxl_filter_walk() to gather create-region targets Dan Williams
2022-12-08 21:29 ` [ndctl PATCH v2 14/18] cxl/region: Trim region size by max available extent Dan Williams
2022-12-09 17:31 ` Alison Schofield
2022-12-08 21:29 ` [ndctl PATCH v2 15/18] cxl/Documentation: Fix whitespace typos in create-region man page Dan Williams
2022-12-09 17:33 ` Alison Schofield
2022-12-09 18:06 ` Dan Williams
2022-12-13 21:17 ` Verma, Vishal L
2022-12-08 21:29 ` [ndctl PATCH v2 16/18] cxl/region: Autoselect memdevs for create-region Dan Williams
2022-12-09 4:08 ` Alison Schofield
2022-12-08 21:29 ` [ndctl PATCH v2 17/18] cxl/test: Extend cxl-topology.sh for a single root-port host-bridge Dan Williams
2022-12-08 21:29 ` [ndctl PATCH v2 18/18] cxl/test: Test single-port host-bridge region creation 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=b509af356cd2f18e3bf847d10e772a0ec701423a.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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