public inbox for nvdimm@lists.linux.dev
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mike Rapoport <rppt@kernel.org>,
	Alison Schofield <alison.schofield@intel.com>,
	Tejun Heo <tj@kernel.org>,
	Marco Crivellari <marco.crivellari@suse.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Dan Williams <dan.j.williams@intel.com>, <nvdimm@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>
Subject: [GIT PULL] NVDIMM for 6.19
Date: Fri, 5 Dec 2025 12:00:54 -0600	[thread overview]
Message-ID: <69331dd6ebdba_50fc7100e3@iweiny-mobl.notmuch> (raw)

Linus,

Please pull from...

  git@gitolite.kernel.org:pub/scm/linux/kernel/git/nvdimm/nvdimm.git tags/libnvdimm-for-6.19

...to get changes for 6.19 for the nvdimm tree.

These are mainly bug fixes and code updates.

There is a new feature to divide up memmap= carve outs and a fix caught in
linux-next for that patch.  Managing memmap memory on the fly for multiple VM's
was proving difficult and Mike provided a driver which allows for the memory to
be better manged.

These have soaked in linux-next without any issues.

Thank you,
Ira Weiny

---
The following changes since commit 6146a0f1dfae5d37442a9ddcba012add260bceb0:

  Linux 6.18-rc4 (2025-11-02 11:28:02 -0800)

are available in the Git repository at:

  git@gitolite.kernel.org:pub/scm/linux/kernel/git/nvdimm/nvdimm.git tags/libnvdimm-for-6.19

for you to fetch changes up to 30065e73d7c018cf2e1bec68e2d6ffafc17b3c25:

  nvdimm: Prevent integer overflow in ramdax_get_config_data() (2025-11-26 10:58:23 -0600)

----------------------------------------------------------------
NVDIMM changes for 6.19

	* nvdimm: Prevent integer overflow in ramdax_get_config_data()
	* Documentation: btt: Unwrap bit 31-30 nested table
	* nvdimm: replace use of system_wq with system_percpu_wq
	* tools/testing/nvdimm: Use per-DIMM device handle
	* nvdimm: allow exposing RAM carveouts as NVDIMM DIMM devices

----------------------------------------------------------------
Alison Schofield (1):
      tools/testing/nvdimm: Use per-DIMM device handle

Bagas Sanjaya (1):
      Documentation: btt: Unwrap bit 31-30 nested table

Dan Carpenter (1):
      nvdimm: Prevent integer overflow in ramdax_get_config_data()

Marco Crivellari (1):
      nvdimm: replace use of system_wq with system_percpu_wq

Mike Rapoport (Microsoft) (1):
      nvdimm: allow exposing RAM carveouts as NVDIMM DIMM devices

 Documentation/driver-api/nvdimm/btt.rst |   2 +-
 drivers/nvdimm/Kconfig                  |  19 +++
 drivers/nvdimm/Makefile                 |   1 +
 drivers/nvdimm/ramdax.c                 | 282 ++++++++++++++++++++++++++++++++
 drivers/nvdimm/security.c               |   4 +-
 tools/testing/nvdimm/test/nfit.c        |   7 +-
 6 files changed, 311 insertions(+), 4 deletions(-)
 create mode 100644 drivers/nvdimm/ramdax.c

             reply	other threads:[~2025-12-05 17:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05 18:00 Ira Weiny [this message]
2025-12-06 19:04 ` [GIT PULL] NVDIMM for 6.19 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=69331dd6ebdba_50fc7100e3@iweiny-mobl.notmuch \
    --to=ira.weiny@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=bagasdotme@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.crivellari@suse.com \
    --cc=nvdimm@lists.linux.dev \
    --cc=rdunlap@infradead.org \
    --cc=rppt@kernel.org \
    --cc=tj@kernel.org \
    --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