From: Dan Williams <dan.j.williams@intel.com>
To: <torvalds@linux-foundation.org>
Cc: <nvdimm@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] NVDIMM and DAX fixes for 6.0-final
Date: Sat, 24 Sep 2022 18:33:50 -0700 [thread overview]
Message-ID: <632faffe84f7c_746b294d1@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/dax-and-nvdimm-fixes-v6.0-final
...to receive a recently discovered one-line fix for devdax that further
addresses a v5.5 regression, and (a bit embarrassing) a small batch of
fixes that have been sitting in my fixes tree for weeks. The older fixes
have soaked in linux-next during that time and address an fsdax infinite
loop and some other minor fixups.
---
The following changes since commit 521a547ced6477c54b4b0cc206000406c221b4d6:
Linux 6.0-rc6 (2022-09-18 13:44:14 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/dax-and-nvdimm-fixes-v6.0-final
for you to fetch changes up to b3bbcc5d1da1b654091dad15980b3d58fdae0fc6:
Merge branch 'for-6.0/dax' into libnvdimm-fixes (2022-09-24 18:14:12 -0700)
----------------------------------------------------------------
dax-and-nvdimm-fixes-v6.0-final
- Fix a infinite loop bug in fsdax
- Fix memory-type detection for devdax (EINJ regression)
- Small cleanups
----------------------------------------------------------------
Andy Shevchenko (1):
nvdimm/namespace: drop nested variable in create_namespace_pmem()
Dan Williams (2):
devdax: Fix soft-reservation memory description
Merge branch 'for-6.0/dax' into libnvdimm-fixes
Jane Chu (1):
pmem: fix a name collision
Li Jinlin (1):
fsdax: Fix infinite loop in dax_iomap_rw()
Shivaprasad G Bhat (1):
ndtest: Cleanup all of blk namespace specific code
drivers/dax/hmem/device.c | 1 +
drivers/nvdimm/namespace_devs.c | 2 -
drivers/nvdimm/pmem.c | 6 +--
fs/dax.c | 3 ++
tools/testing/nvdimm/test/ndtest.c | 77 --------------------------------------
5 files changed, 7 insertions(+), 82 deletions(-)
next reply other threads:[~2022-09-25 1:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 1:33 Dan Williams [this message]
2022-09-25 16:08 ` 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=632faffe84f7c_746b294d1@dwillia2-mobl3.amr.corp.intel.com.notmuch \
--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
all inboxes | Powered by JetHome®