From: <dan.j.williams@intel.com>
To: "Michał Cłapiński" <mclapinski@google.com>,
"Ira Weiny" <ira.weiny@intel.com>
Cc: <dan.j.williams@intel.com>, Mike Rapoport <rppt@kernel.org>,
Dave Jiang <dave.jiang@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>, <jane.chu@oracle.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
"Tyler Hicks" <code@tyhicks.com>, <linux-kernel@vger.kernel.org>,
<nvdimm@lists.linux.dev>
Subject: Re: [PATCH 1/1] nvdimm: allow exposing RAM carveouts as NVDIMM DIMM devices
Date: Tue, 13 Jan 2026 18:34:35 -0800 [thread overview]
Message-ID: <696700bba6f6a_207181006c@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <CAAi7L5e3TFcuwpt5vzy_xOtDxX0AfgH3tDzZJM=uiJy4h9a08A@mail.gmail.com>
Michał Cłapiński wrote:
[..]
> > Did yall have a suggestion on how? I lost track of this thread over the
> > holidays and so I'm not sure where this stands.
> >
> > Ira
>
> I think Dan's change needs to skip devm_request_mem_region if offset
> == 0 in __dax_pmem_probe in drivers/dax/pmem.c.
I would be happy to review a fixup patch that works for you, and give
you Co-developed-by credit. That would be faster than waiting for this
to bubble back up to the top my queue again.
next prev parent reply other threads:[~2026-01-14 2:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 8:04 [PATCH 0/1] nvdimm: allow exposing RAM as libnvdimm DIMMs Mike Rapoport
2025-08-26 8:04 ` [PATCH 1/1] nvdimm: allow exposing RAM carveouts as NVDIMM DIMM devices Mike Rapoport
2025-08-29 0:47 ` Ira Weiny
2025-08-29 7:57 ` Mike Rapoport
2025-09-01 16:01 ` Michał Cłapiński
2025-09-02 15:35 ` Mike Rapoport
2025-09-24 1:16 ` dan.j.williams
2025-09-26 12:47 ` Michał Cłapiński
2025-09-26 18:45 ` dan.j.williams
2025-09-30 10:15 ` Mike Rapoport
2025-10-01 14:14 ` Michał Cłapiński
2025-10-01 22:28 ` dan.j.williams
2025-12-09 20:10 ` Michał Cłapiński
2025-12-17 3:14 ` dan.j.williams
2025-12-29 16:39 ` Michał Cłapiński
2026-01-12 23:36 ` Ira Weiny
2026-01-13 12:39 ` Michał Cłapiński
2026-01-14 2:34 ` dan.j.williams [this message]
2025-09-24 1:08 ` dan.j.williams
2025-09-30 10:11 ` Mike Rapoport
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=696700bba6f6a_207181006c@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=code@tyhicks.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=jane.chu@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mclapinski@google.com \
--cc=nvdimm@lists.linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.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
all inboxes | Powered by JetHome®