From: Dan Williams <dan.j.williams@intel.com>
To: <torvalds@linux-foundation.org>
Cc: <nvdimm@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] NVDIMM for 6.1
Date: Fri, 14 Oct 2022 16:44:03 -0700 [thread overview]
Message-ID: <6349f4435df76_7ddc2943e@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-6.1
...to receive some small cleanups and fixes in and around the nvdimm
subsystem. The most significant change is a regression fix for nvdimm
namespace (volume) creation when the namespace size is smaller than 2MB.
It has appeared in linux-next with no reported issues.
---
The following changes since commit 521a547ced6477c54b4b0cc206000406c221b4d6:
Linux 6.0-rc6 (2022-09-18 13:44:14 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-6.1
for you to fetch changes up to 305a72efa791c826fe84768ca55e31adc4113ea8:
Merge branch 'for-6.1/nvdimm' into libnvdimm-for-next (2022-10-01 19:16:16 -0700)
----------------------------------------------------------------
libnvdimm for 6.1
- Fix nvdimm namespace creation on platforms that do not publish
associated 'DIMM' metadata for a persistent memory region.
- Miscellaneous fixes and cleanups.
----------------------------------------------------------------
Andy Shevchenko (2):
nvdimm/namespace: return uuid_null only once in nd_dev_to_uuid()
nvdimm/namespace: drop unneeded temporary variable in size_store()
Bo Liu (1):
dax: Remove usage of the deprecated ida_simple_xxx API
Dan Williams (1):
Merge branch 'for-6.1/nvdimm' into libnvdimm-for-next
Jason Wang (1):
nvdimm/namespace: Fix comment typo
Jiapeng Chong (2):
nvdimm/region: Fix kernel-doc
nvdimm: make __nvdimm_security_overwrite_query static
Lin Yujun (1):
ACPI: HMAT: Release platform device in case of platform_device_add_data() fails
Tyler Hicks (1):
libnvdimm/region: Allow setting align attribute on regions without mappings
drivers/dax/hmem/device.c | 4 ++--
drivers/dax/super.c | 6 +++---
drivers/nvdimm/namespace_devs.c | 24 ++++++++----------------
drivers/nvdimm/region_devs.c | 10 ++++------
drivers/nvdimm/security.c | 2 +-
5 files changed, 18 insertions(+), 28 deletions(-)
next reply other threads:[~2022-10-14 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 23:44 Dan Williams [this message]
2022-10-15 1:44 ` 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=6349f4435df76_7ddc2943e@dwillia2-mobl3.amr.corp.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--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®