From: Dan Williams <dan.j.williams@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] libnvdimm + device-dax for v5.12-rc1
Date: Tue, 23 Feb 2021 18:47:38 -0800 [thread overview]
Message-ID: <CAPcyv4i1-mwp8B0Y_hR44rGh9qUPuDiZeiUFJ_TJzvPoENa-pQ@mail.gmail.com> (raw)
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-for-5.12
...to receive some miscellaneous cleanups and a fix for v5.12. This
mainly continues the kernel wide effort to remove a return code from
the remove() callback in the driver model. The fix addresses a return
code polarity typo in the new sysfs attribute to manually specify a
device-dax instance mapping range. This has all appeared in -next with
no reported issues.
---
The following changes since commit 1048ba83fb1c00cd24172e23e8263972f6b5d9ac:
Linux 5.11-rc6 (2021-01-31 13:50:09 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-for-5.12
for you to fetch changes up to 64ffe84320745ea836555ad207ebfb0e896b6167:
Merge branch 'for-5.12/dax' into for-5.12/libnvdimm (2021-02-23
18:13:45 -0800)
----------------------------------------------------------------
libnvdimm + device-dax for 5.12
- Fix the error code polarity for the device-dax/mapping attribute
- For the device-dax and libnvdimm bus implementations stop implementing
a useless return code for the remove() callback.
- Miscellaneous cleanups
----------------------------------------------------------------
Dan Williams (1):
Merge branch 'for-5.12/dax' into for-5.12/libnvdimm
Shiyang Ruan (1):
device-dax: Fix default return code of range_parse()
Uwe Kleine-König (7):
libnvdimm/dimm: Simplify nvdimm_remove()
libnvdimm: Make remove callback return void
device-dax: Prevent registering drivers without probe callback
device-dax: Properly handle drivers without remove callback
device-dax: Fix error path in dax_driver_register
device-dax: Drop an empty .remove callback
dax-device: Make remove callback return void
drivers/dax/bus.c | 24 +++++++++++++++++++++---
drivers/dax/bus.h | 2 +-
drivers/dax/device.c | 8 +-------
drivers/dax/kmem.c | 7 ++-----
drivers/dax/pmem/compat.c | 3 +--
drivers/nvdimm/blk.c | 3 +--
drivers/nvdimm/bus.c | 13 +++++--------
drivers/nvdimm/dimm.c | 7 +------
drivers/nvdimm/pmem.c | 4 +---
drivers/nvdimm/region.c | 4 +---
include/linux/nd.h | 2 +-
11 files changed, 36 insertions(+), 41 deletions(-)
next reply other threads:[~2021-02-24 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 2:47 Dan Williams [this message]
2021-02-24 18:46 ` [GIT PULL] libnvdimm + device-dax for v5.12-rc1 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=CAPcyv4i1-mwp8B0Y_hR44rGh9qUPuDiZeiUFJ_TJzvPoENa-pQ@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.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;
as well as URLs for NNTP newsgroup(s).