From: Dan Williams <dan.j.williams@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux NVDIMM <nvdimm@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] nvdimm fixes for v5.15-rc4
Date: Fri, 1 Oct 2021 18:19:12 -0700 [thread overview]
Message-ID: <CAPcyv4iEHttW7fDzaKYdAr2t4w3YJQ7t7QtadO0bZKDWPuK0Ag@mail.gmail.com> (raw)
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-fixes-5.15-rc4
...to receive a fix for a regression added this cycle in the pmem
driver, and for a long standing bug for failed NUMA node lookups on
ARM64.
This has appeared in -next for several days with no reported issues.
Please pull, thanks.
---
The following changes since commit 5816b3e6577eaa676ceb00a848f0fd65fe2adc29:
Linux 5.15-rc3 (2021-09-26 14:08:19 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-fixes-5.15-rc4
for you to fetch changes up to d55174cccac2e4c2a58ff68b6b573fc0836f73bd:
nvdimm/pmem: fix creating the dax group (2021-09-27 11:40:43 -0700)
----------------------------------------------------------------
libnvdimm fixes for v5.15-rc4
- Fix a regression that caused the sysfs ABI for pmem block devices to
not be registered. This fails the nvdimm unit tests and dax xfstests.
- Fix numa node lookups for dax-kmem memory (device-dax memory assigned
to the page allocator) on ARM64.
----------------------------------------------------------------
Christoph Hellwig (1):
nvdimm/pmem: fix creating the dax group
Jia He (1):
ACPI: NFIT: Use fallback node id when numa info in NFIT table is incorrect
drivers/acpi/nfit/core.c | 12 ++++++++++++
drivers/nvdimm/pmem.c | 5 +----
2 files changed, 13 insertions(+), 4 deletions(-)
next reply other threads:[~2021-10-02 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 1:19 Dan Williams [this message]
2021-10-02 18:07 ` [GIT PULL] nvdimm fixes for v5.15-rc4 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=CAPcyv4iEHttW7fDzaKYdAr2t4w3YJQ7t7QtadO0bZKDWPuK0Ag@mail.gmail.com \
--to=dan.j.williams@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).