mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dan Williams <djbw@kernel.org>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Alison Schofield <alison.schofield@intel.com>,
	Ira Weiny <iweiny@kernel.org>, <nvdimm@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>
Subject: [GIT PULL] NVDIMM and DAX for 7.2
Date: Thu, 18 Jun 2026 10:13:20 -0700	[thread overview]
Message-ID: <ajQnMABCFUbVndvc@aschofie-mobl2.lan> (raw)

Hi Linus,

Please pull to receive a small set of NVDIMM and DAX changes. Also
included are updates to the MAINTAINER file, one which adds me as
I'm picking up the patch wrangling role from Ira Weiny.

All have been soaking in linux-next for a couple of weeks.

Thanks,
Alison Schofield

---
The following changes since commit e43ffb69e0438cddd72aaa30898b4dc446f664f8:

  Linux 7.1-rc6 (2026-05-31 15:14:24 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git tags/libnvdimm-for-7.2

for you to fetch changes up to 86e411b6ec277dbb8ac1f1d855dc337181a62a29:

  MAINTAINERS: nvdimm: Include maintainer profile (2026-06-01 18:06:08 -0700)

----------------------------------------------------------------
Updates for the 7.2 release

A race condition and a couple of static analysis issues are fixed in BTT
Use sysfs_emit() in preparation for removal of cpumap_print_to_pagebuf()
Escalate a dev_dbg to dev_err in a resource conflict message
MAINTAINER file updates

----------------------------------------------------------------
Abdun Nihaal (2):
      nvdimm/btt: Free arena sub-allocations on discover_arenas() error path
      nvdimm/btt: Free arenas on btt_init() error paths

Alison Schofield (1):
      nvdimm/btt: Handle preemption in BTT lane acquisition

Dave Jiang (1):
      MAINTAINERS: Add maintainer info for libnvdimm and DAX

Ira Weiny (1):
      MAINTAINERS: Update address for Ira Weiny

Krzysztof Kozlowski (1):
      MAINTAINERS: nvdimm: Include maintainer profile

Tomasz Wolski (1):
      dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region()

Yury Norov (1):
      nvdimm: Use sysfs_emit() for cpumask show callback

 .mailmap                                |  1 +
 Documentation/driver-api/nvdimm/btt.rst |  5 ++---
 MAINTAINERS                             | 11 ++++++++---
 drivers/dax/bus.c                       |  2 +-
 drivers/nvdimm/btt.c                    | 14 ++++++++++----
 drivers/nvdimm/nd.h                     | 11 +++++------
 drivers/nvdimm/nd_perf.c                |  2 +-
 drivers/nvdimm/region_devs.c            | 66 ++++++++++++++++++++++--------------------------------------------
 8 files changed, 50 insertions(+), 62 deletions(-)

             reply	other threads:[~2026-06-18 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 17:13 Alison Schofield [this message]
2026-06-18 23:35 ` Linus Torvalds
2026-06-22  2:07   ` Ira Weiny
2026-06-19  0:09 ` 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=ajQnMABCFUbVndvc@aschofie-mobl2.lan \
    --to=alison.schofield@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=djbw@kernel.org \
    --cc=iweiny@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=vishal.l.verma@intel.com \
    /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

Powered by JetHome