From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Davidlohr Bueso <dave@stgolabs.net>,
"Alison Schofield" <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
<linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 1/2] cxl/memdev: Remove unused partition values
Date: Thu, 30 Jan 2025 13:44:00 +0000 [thread overview]
Message-ID: <20250130134400.00007247@huawei.com> (raw)
In-Reply-To: <20250128-rfc-rearch-mem-res-v1-1-26d1ca151376@intel.com>
On Tue, 28 Jan 2025 12:51:07 -0600
Ira Weiny <ira.weiny@intel.com> wrote:
> The next volatile and next persistent values are unused and are
> cluttering the cxl_memdev_state.
>
> Remove these values.
>
> Signed-off-by: Ira Weiny <ira.weiny@intel.com>
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
next prev parent reply other threads:[~2025-01-30 13:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 18:51 [PATCH RFC 0/2] cxl: Further clean up of memdev state Ira Weiny
2025-01-28 18:51 ` [PATCH RFC 1/2] cxl/memdev: Remove unused partition values Ira Weiny
2025-01-29 8:58 ` Alejandro Lucero Palau
2025-01-29 15:09 ` Davidlohr Bueso
2025-01-29 16:51 ` Dave Jiang
2025-01-30 13:44 ` Jonathan Cameron [this message]
2025-02-04 20:59 ` Dan Williams
2025-02-04 23:59 ` Fan Ni
2025-01-28 18:51 ` [PATCH RFC 2/2] cxl/memdev: Remove temporary variables from cxl_memdev_state Ira Weiny
2025-01-29 9:08 ` Alejandro Lucero Palau
2025-01-29 16:32 ` Ira Weiny
2025-01-29 18:17 ` Alejandro Lucero Palau
2025-01-29 21:16 ` Ira Weiny
2025-01-29 16:52 ` Dave Jiang
2025-01-30 0:15 ` Davidlohr Bueso
2025-01-30 13:52 ` Jonathan Cameron
2025-01-30 15:14 ` Ira Weiny
2025-02-04 21:39 ` Dan Williams
2025-02-04 23:37 ` Ira Weiny
2025-02-05 0:15 ` Dan Williams
2025-02-05 9:01 ` Alejandro Lucero Palau
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=20250130134400.00007247@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@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.