From: Dan Williams <dan.j.williams@intel.com>
To: <torvalds@linux-foundation.org>
Cc: <linux-cxl@vger.kernel.org>, <nvdimm@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Compute Express Link (CXL) fixes for 6.2-final
Date: Fri, 10 Feb 2023 18:42:13 -0800 [thread overview]
Message-ID: <63e700859e02a_88e1294d6@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl tags/cxl-fixes-6.2
...to receive 2 fixups for CXL in presence of passthrough decoders. This
primarily helps developers using the QEMU CXL emulation, but with the
impending arrival of CXL switches these types of topologies will be of
interest to end users.
The first commit has appeared in -next for several days with no issues.
The second has not aged as long, but has been verified by new unit
tests.
---
The following changes since commit 6d796c50f84ca79f1722bb131799e5a5710c4700:
Linux 6.2-rc6 (2023-01-29 13:59:43 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl tags/cxl-fixes-6.2
for you to fetch changes up to 711442e29f16f0d39dd0e2460c9baacfccb9d5a7:
cxl/region: Fix passthrough-decoder detection (2023-02-07 11:04:30 -0800)
----------------------------------------------------------------
cxl fixes for 6.2
- Fix a crash when shutting down regions in the presence of passthrough
decoders
- Fix region creation to understand passthrough decoders instead of the
narrower definition of passthrough ports
----------------------------------------------------------------
Dan Williams (1):
cxl/region: Fix passthrough-decoder detection
Fan Ni (1):
cxl/region: Fix null pointer dereference for resetting decoder
drivers/cxl/core/region.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
next reply other threads:[~2023-02-11 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 2:42 Dan Williams [this message]
2023-02-11 19:11 ` pr-tracker-bot
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=63e700859e02a_88e1294d6@dwillia2-mobl3.amr.corp.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®