From: Ira Weiny <ira.weiny@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <nvdimm@lists.linux.dev>,
Davidlohr Bueso <dave@stgolabs.net>,
"Jiang, Dave" <dave.jiang@intel.com>, Li Chen <me@linux.beauty>,
Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [GIT PULL] NVDIMM and DAX for 7.0
Date: Wed, 11 Feb 2026 15:09:16 -0600 [thread overview]
Message-ID: <698ceffc62269_10ad1610081@iweiny-mobl.notmuch> (raw)
Linus,
Pleas pull from...
git@gitolite.kernel.org:pub/scm/linux/kernel/git/nvdimm/nvdimm.git tags/libnvdimm-for-7.0
... to get changes for 7.0 for the nvdimm tree.
There is a kmap conversion and a bug fix this go around. The bug fix was only
reported in the last rc so it got added here.
These have soaked in linux-next for a week without issues.
Thank you,
Ira Weiny
---
The following changes since commit 63804fed149a6750ffd28610c5c1c98cce6bd377:
Linux 6.19-rc7 (2026-01-25 14:11:24 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/nvdimm/nvdimm.git tags/libnvdimm-for-7.0
for you to fetch changes up to a9ba6733c7f1096c4506bf4e34a546e07242df74:
nvdimm: virtio_pmem: serialize flush requests (2026-02-04 13:16:40 -0600)
----------------------------------------------------------------
Updates for the 7.0 release
* nvdimm: virtio_pmem: serialize flush requests
* drivers/nvdimm: Use local kmaps
----------------------------------------------------------------
Davidlohr Bueso (1):
drivers/nvdimm: Use local kmaps
Li Chen (1):
nvdimm: virtio_pmem: serialize flush requests
drivers/nvdimm/btt.c | 12 ++++++------
drivers/nvdimm/nd_virtio.c | 3 ++-
drivers/nvdimm/pmem.c | 8 ++++----
drivers/nvdimm/virtio_pmem.c | 1 +
drivers/nvdimm/virtio_pmem.h | 4 ++++
5 files changed, 17 insertions(+), 11 deletions(-)
next reply other threads:[~2026-02-11 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 21:09 Ira Weiny [this message]
2026-02-13 1:18 ` 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=698ceffc62269_10ad1610081@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=me@linux.beauty \
--cc=mst@redhat.com \
--cc=nvdimm@lists.linux.dev \
--cc=pankaj.gupta.linux@gmail.com \
--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®