linux-cxl.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Widawsky <ben.widawsky@intel.com>
To: linux-cxl@vger.kernel.org
Cc: Ben Widawsky <ben.widawsky@intel.com>,
	Alison Schofield <alison.schofield@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Ira Weiny <ira.weiny@intel.com>,
	Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
	Vishal Verma <vishal.l.verma@intel.com>
Subject: [PATCH 0/3] Decoder prep patches
Date: Mon, 13 Sep 2021 09:33:21 -0700	[thread overview]
Message-ID: <20210913163324.1008564-1-ben.widawsky@intel.com> (raw)

This small series are the less controversial patches from the cxl_mem driver
series I posted previously [1]. It includes some small doc fixups and the final
nail in the coffin of the earlier cxl_mem rename to cxl_pci [2].

[1]: https://lore.kernel.org/linux-cxl/20210902195017.2516472-1-ben.widawsky@intel.com/
[2]: https://lore.kernel.org/linux-cxl/20210526174413.802913-1-ben.widawsky@intel.com/

Ben Widawsky (3):
  Documentation/cxl: Add bus internal docs
  cxl/core/bus: Document and tighten up decoder API
  cxl/pci: Disambiguate cxl_pci further from cxl_mem

 .../driver-api/cxl/memory-devices.rst         |  3 +
 drivers/cxl/acpi.c                            |  4 +-
 drivers/cxl/core/bus.c                        | 36 ++++++++--
 drivers/cxl/cxl.h                             |  3 +-
 drivers/cxl/pci.c                             | 68 ++++++++++---------
 5 files changed, 71 insertions(+), 43 deletions(-)

-- 
2.33.0


             reply	other threads:[~2021-09-13 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 16:33 Ben Widawsky [this message]
2021-09-13 16:33 ` [PATCH 1/3] Documentation/cxl: Add bus internal docs Ben Widawsky
2021-09-13 16:33 ` [PATCH 2/3] cxl/core/bus: Document and tighten up decoder API Ben Widawsky
2021-09-14  0:11   ` Ben Widawsky
2021-09-13 16:33 ` [PATCH 3/3] cxl/pci: Disambiguate cxl_pci further from cxl_mem Ben Widawsky

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=20210913163324.1008564-1-ben.widawsky@intel.com \
    --to=ben.widawsky@intel.com \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=alison.schofield@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;
as well as URLs for NNTP newsgroup(s).