From: Ira Weiny <ira.weiny@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-cxl@vger.kernel.org>,
<nvdimm@lists.linux.dev>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Nathan Chancellor <nathan@kernel.org>,
Dave Jiang <dave.jiang@intel.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>
Subject: [GIT PULL] NVDIMM for 6.17
Date: Wed, 30 Jul 2025 14:57:40 -0500 [thread overview]
Message-ID: <688a7934c0caf_1028b3294db@iweiny-mobl.notmuch> (raw)
Hey Linus, please pull from:
https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git/ tags/libnvdimm-for-6.17
... to get header file cleanups. Specifically use specific headers rather
than just kernel.h in libnvdimm.h to reduce header file usage.
The second patch is a fix to CXL but is going through my tree as the
libnvdimm patch caused the issue.
Thanks,
Ira
---
The following changes since commit d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af:
Linux 6.16-rc4 (2025-06-29 13:09:04 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git/ tags/libnvdimm-for-6.17
for you to fetch changes up to 9f97e61bde6a91a429f48da1a461488a15b01813:
cxl: Include range.h in cxl.h (2025-07-01 11:15:13 -0500)
----------------------------------------------------------------
libnvdimm fixes for 6.17
- Remove kernel.h from libnvdimm.h
- Fix build issue found later in next
----------------------------------------------------------------
Andy Shevchenko (1):
libnvdimm: Don't use "proxy" headers
Nathan Chancellor (1):
cxl: Include range.h in cxl.h
drivers/cxl/cxl.h | 1 +
include/linux/libnvdimm.h | 15 ++++++++++-----
2 files changed, 11 insertions(+), 5 deletions(-)
next reply other threads:[~2025-07-30 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 19:57 Ira Weiny [this message]
2025-07-31 20:50 ` [GIT PULL] NVDIMM for 6.17 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=688a7934c0caf_1028b3294db@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@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