Linux CXL
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: <ira.weiny@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	Ben Widawsky <ben.widawsky@intel.com>,
	Alison Schofield <alison.schofield@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	<linux-cxl@vger.kernel.org>
Subject: Re: [INTERNAL PATCH 2/2] cxl/cxlmem: Change cxl_mem to a more descriptive name
Date: Wed, 10 Nov 2021 17:40:10 +0000	[thread overview]
Message-ID: <20211110174010.000055c2@Huawei.com> (raw)
In-Reply-To: <20211102202901.3675568-3-ira.weiny@intel.com>

On Tue, 2 Nov 2021 13:29:01 -0700
<ira.weiny@intel.com> wrote:

> From: Ira Weiny <ira.weiny@intel.com>
> 
> The cxl_mem object actually represents the state of a CXL device within the
> driver.  This is data layered on top of the PCI or other device.  Even though
> the only device currently represented is a memory device, calling this cxl_mem
> is confusing because this is not solely a CXL memory device.  Furthermore,
> cxl_memdev does drive a CXL memory device.  So changing the name helps to
> distinguish these to structures.
> 
> Update the structure name, function names, and the kdocs to reflect the
> real uses of this structure.
> 
> Acked-by: Ben Widawsky <ben.widawsky@intel.com>
> Signed-off-by: Ira Weiny <ira.weiny@intel.com>
> 

...

>  struct cxl_memdev *
> -devm_cxl_add_memdev(struct cxl_mem *cxlm)
> +devm_cxl_add_memdev(struct cxl_dev_state *cxlds)
Just noticed on a read through (I'm trying to catch up with recent changes)

Combine the above 2 lines into one.  Could do it as a tidy up
patch if too late to fold into this patch.

Thanks,

Jonathan


>  {
>  	struct cxl_memdev *cxlmd;
>  	struct device *dev;
>  	struct cdev *cdev;

  parent reply	other threads:[~2021-11-10 17:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 20:28 [INTERNAL PATCH 0/2] CXL: Clarify struct cxl_mem ira.weiny
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   ` Jonathan Cameron [this message]
2021-11-10 19:01     ` [INTERNAL PATCH 2/2] cxl/cxlmem: Change cxl_mem to a more descriptive name 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=20211110174010.000055c2@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=ben.widawsky@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ira.weiny@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