All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: linux-cxl@vger.kernel.org
Cc: alejandro.lucero-palau@amd.com, dan.j.williams@intel.com,
	ira.weiny@intel.com, vishal.l.verma@intel.com,
	alison.schofield@intel.com, Jonathan.Cameron@huawei.com,
	dave@stgolabs.net, fan.ni@samsung.com
Subject: [PATCH 0/3 v3] cxl: Pull out mailbox bits to be independent of cxl_dev_state
Date: Tue,  3 Sep 2024 16:59:07 -0700	[thread overview]
Message-ID: <20240904000020.1686611-1-dave.jiang@intel.com> (raw)

Hi Alejandro,
Please feel free to pull in the patches in this series into your type2 series.
Although I may just pull these into the 6.12 merge window to make things easier
for you.

The patches pulls out the related mailbox bits and form a 'struct cxl_mailbox'. In
v2 Jonathan suggested that we keep cxl_mbox embedded. So I moved it back to be
embedded. For the type2 devices that does not use mailbox, it can just not have
the mailbox struct at all.

v3
- moved the other cxl headers into the linux/cxl directory.
- Moved rcuwait.h header into mailbox.h (Alison)

---

Dave Jiang (3):
      cxl: Move mailbox related bits to the same context
      cxl: Convert cxl_internal_send_cmd() to use 'struct cxl_mailbox' as input
      cxl: move cxl headers to new linux/cxl/ directory

 MAINTAINERS                                |  3 +-
 drivers/acpi/apei/einj-cxl.c               |  2 +-
 drivers/acpi/apei/ghes.c                   |  2 +-
 drivers/cxl/core/mbox.c                    | 91 ++++++++++++++++++++++++++++++++------------------
 drivers/cxl/core/memdev.c                  | 41 +++++++++++++----------
 drivers/cxl/core/port.c                    |  2 +-
 drivers/cxl/cxlmem.h                       | 25 ++++++--------
 drivers/cxl/pci.c                          | 82 ++++++++++++++++++++++++++++++---------------
 drivers/cxl/pmem.c                         | 10 ++++--
 drivers/cxl/security.c                     | 23 +++++++------
 include/linux/{einj-cxl.h => cxl/einj.h}   |  0
 include/linux/{cxl-event.h => cxl/event.h} |  0
 include/linux/cxl/mailbox.h                | 28 ++++++++++++++++
 tools/testing/cxl/test/mem.c               | 44 ++++++++++++++++++------
 14 files changed, 233 insertions(+), 120 deletions(-)


             reply	other threads:[~2024-09-04  0:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 23:59 Dave Jiang [this message]
2024-09-03 23:59 ` [PATCH v3 1/3] cxl: Move mailbox related bits to the same context Dave Jiang
2024-09-04 16:30   ` Alison Schofield
2024-09-04 16:49     ` Dave Jiang
2024-09-05  5:04   ` Dan Carpenter
2024-09-03 23:59 ` [PATCH v3 2/3] cxl: Convert cxl_internal_send_cmd() to use 'struct cxl_mailbox' as input Dave Jiang
2024-09-03 23:59 ` [PATCH v3 3/3] cxl: move cxl headers to new linux/cxl/ directory Dave Jiang
2024-09-04  6:52   ` Alejandro Lucero Palau
2024-09-04 15:35     ` Dave Jiang
2024-09-05  2:55     ` Dan Williams
2024-09-05  6:51       ` Alejandro Lucero Palau
2024-09-05 20:21         ` Dave Jiang

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=20240904000020.1686611-1-dave.jiang@intel.com \
    --to=dave.jiang@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=alejandro.lucero-palau@amd.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave@stgolabs.net \
    --cc=fan.ni@samsung.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 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.