NVDIMM Device and Persistent Memory development
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Ira Weiny <ira.weiny@intel.com>, <nvdimm@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <linux-cxl@vger.kernel.org>
Subject: [GIT PULL] NVDIMM for 6.7
Date: Wed, 1 Nov 2023 17:25:30 -0700	[thread overview]
Message-ID: <6542ec7ae6233_4dfae294bb@iweiny-mobl.notmuch> (raw)

Hi Linus, please pull from:

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

... to get updates to the nvdimm tree.  They are a mix of bug fixes and updates
to interfaces used by nvdimm.

Bug fixes include:
	Fix a sleep during spinlock in PREEMPT_RT kernels when getting a BTT
		lane
	Check for kstrdup memory failure in region probe
	Use the correct variables in the nvdimm_badblocks_populate() kdoc block

Updates to interfaces include:
	Use devm_kstrdup to manage memory better
	Allow class structures to be declared at build time
	Start using __counted_by to help with bounds checking
	Remove use of the deprecated strncpy

They have all been in -next for more than a week with no reported issues.

---

The following changes since commit 6465e260f48790807eef06b583b38ca9789b6072:

  Linux 6.6-rc3 (2023-09-24 14:31:13 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 9ea459e477dc09370cdd8ee13b61aefe8cd1f20a:

  libnvdimm: remove kernel-doc warnings: (2023-10-18 09:48:05 -0700)

----------------------------------------------------------------
libnvdimm updates for v6.7

- updates to deprecated and changed interfaces
- bug/kdoc fixes

----------------------------------------------------------------
Chen Ni (1):
      libnvdimm/of_pmem: Use devm_kstrdup instead of kstrdup and check its return value

Greg Kroah-Hartman (1):
      testing: nvdimm: make struct class structures constant

Justin Stitt (1):
      dax: refactor deprecated strncpy

Kees Cook (1):
      libnvdimm: Annotate struct nd_region with __counted_by

Tomas Glozar (1):
      nd_btt: Make BTT lanes preemptible

Zhu Wang (1):
      libnvdimm: remove kernel-doc warnings:

 drivers/dax/bus.c                  |  2 +-
 drivers/nvdimm/badrange.c          |  4 ++--
 drivers/nvdimm/nd.h                |  2 +-
 drivers/nvdimm/of_pmem.c           |  8 +++++++-
 drivers/nvdimm/region_devs.c       | 10 +++++-----
 tools/testing/nvdimm/test/ndtest.c | 17 +++++++++--------
 tools/testing/nvdimm/test/nfit.c   | 14 +++++++-------
 7 files changed, 32 insertions(+), 25 deletions(-)

             reply	other threads:[~2023-11-02  0:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  0:25 Ira Weiny [this message]
2023-11-03  1:26 ` [GIT PULL] NVDIMM for 6.7 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=6542ec7ae6233_4dfae294bb@iweiny-mobl.notmuch \
    --to=ira.weiny@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=linux-cxl@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).