From: ira.weiny@intel.com
To: Dan Williams <dan.j.williams@intel.com>
Cc: Ira Weiny <ira.weiny@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ben Widawsky <ben.widawsky@intel.com>,
linux-cxl@vger.kernel.org
Subject: [INTERNAL PATCH 0/2] CXL: Clarify struct cxl_mem
Date: Tue, 2 Nov 2021 13:28:59 -0700 [thread overview]
Message-ID: <20211102202901.3675568-1-ira.weiny@intel.com> (raw)
From: Ira Weiny <ira.weiny@intel.com>
The first patch is a simple clean up.
The cxl_mem object actually represents the state of a CXL device within the
driver. Furthermore, there was confusion with the cxl_memdev structure.
Clean this up with a new structure name, function names and kernel docs.
---
Changes made based on Ben's comments.
Ira Weiny (2):
cxl/mbox: Remove bad comment
cxl/cxlmem: Change cxl_mem to a more descriptive name
drivers/cxl/core/mbox.c | 184 +++++++++++++++++------------------
drivers/cxl/core/memdev.c | 48 ++++-----
drivers/cxl/cxlmem.h | 35 ++++---
drivers/cxl/pci.c | 146 +++++++++++++--------------
drivers/cxl/pmem.c | 39 ++++----
tools/testing/cxl/test/mem.c | 50 +++++-----
6 files changed, 252 insertions(+), 250 deletions(-)
--
2.28.0.rc0.12.gb6a658bd00c9
next reply other threads:[~2021-11-02 20:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 20:28 ira.weiny [this message]
2021-11-02 20:29 ` [INTERNAL PATCH 1/2] cxl/mbox: Remove bad comment ira.weiny
2021-11-02 20:29 ` [INTERNAL PATCH 2/2] cxl/cxlmem: Change cxl_mem to a more descriptive name ira.weiny
2021-11-03 1:53 ` Dan Williams
2021-11-03 13:51 ` Jonathan Cameron
2021-11-03 16:38 ` Dan Williams
2021-11-03 20:41 ` [PATCH] cxl/cxlmem: Remove unused cxlmd field ira.weiny
2021-11-03 22:13 ` Dan Williams
2021-11-03 22:34 ` Ben Widawsky
2021-11-10 17:40 ` [INTERNAL PATCH 2/2] cxl/cxlmem: Change cxl_mem to a more descriptive name Jonathan Cameron
2021-11-10 19:01 ` Ira Weiny
2021-11-02 20:34 ` [INTERNAL PATCH 0/2] CXL: Clarify struct cxl_mem Ira Weiny
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=20211102202901.3675568-1-ira.weiny@intel.com \
--to=ira.weiny@intel.com \
--cc=alison.schofield@intel.com \
--cc=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox