NVDIMM Device and Persistent Memory development
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Vishal Verma <vishal.l.verma@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Ira Weiny <ira.weiny@intel.com>,
	"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] NVDIMM//DAX changes for 6.9
Date: Thu, 14 Mar 2024 13:44:39 -0700	[thread overview]
Message-ID: <6ea8ea30-9a6b-4ed1-bccc-96b0171a3dd2@intel.com> (raw)

Hi Linus, please pull from:

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

... to get updates to the nvdimm tree. They are a number of updates to interfaces used by nvdimm/dax and a documentation fix.

Doc fixes:
	ACPI_NFIT Kconfig documetation fix

Updates:
	Make nvdimm_bus_type and dax_bus_type const
	Remove SLAB_MEM_SPREAD flag usage in DAX

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

---

The following changes since commit 54be6c6c5ae8e0d93a6c4641cb7528eb0b6ba478:

  Linux 6.8-rc3 (2024-02-04 12:20:36 +0000)

are available in the Git repository at:

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

for you to fetch changes up to d9212b35da52109361247b66010802d43c6b1f0d:

  dax: remove SLAB_MEM_SPREAD flag usage (2024-03-04 09:10:37 -0700)

----------------------------------------------------------------
libnvdimm updates for v6.9

- ACPI_NFIT Kconfig documetation fix
- Make nvdimm_bus_type const
- Make dax_bus_type const
- remove SLAB_MEM_SPREAD flag usage in DAX

----------------------------------------------------------------
Chengming Zhou (1):
      dax: remove SLAB_MEM_SPREAD flag usage

Peter Robinson (1):
      libnvdimm: Fix ACPI_NFIT in BLK_DEV_PMEM help

Ricardo B. Marliere (2):
      nvdimm: make nvdimm_bus_type const
      device-dax: make dax_bus_type const

 drivers/dax/bus.c      | 2 +-
 drivers/dax/super.c    | 2 +-
 drivers/nvdimm/Kconfig | 2 +-
 drivers/nvdimm/bus.c   | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

             reply	other threads:[~2024-03-14 20:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 20:44 Dave Jiang [this message]
2024-03-15 20:37 ` [GIT PULL] NVDIMM//DAX changes for 6.9 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=6ea8ea30-9a6b-4ed1-bccc-96b0171a3dd2@intel.com \
    --to=dave.jiang@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ira.weiny@intel.com \
    --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).