From: cp0613@linux.alibaba.com
To: buildroot@buildroot.org
Cc: ju.o@free.fr, Chen Pei <cp0613@linux.alibaba.com>
Subject: [Buildroot] [PATCH v2 0/2] package/ndctl: new package
Date: Tue, 10 Mar 2026 16:18:48 +0800 [thread overview]
Message-ID: <20260310081850.33001-1-cp0613@linux.alibaba.com> (raw)
From: Chen Pei <cp0613@linux.alibaba.com>
ndctl is a userspace utility for managing persistent memory (PMEM) and
NVDIMM devices on Linux, enabling configuration and monitoring of
namespaces, regions, and health status.
Adding ndctl to Buildroot allows embedded or server systems with PMEM
hardware to manage persistent memory directly on the target device in
a lightweight, self-contained manner.
I have submitted a patch to upstream regarding the issue caused by
disabling fwctl and keyutils. Currently, considering they will actually
be used, I've decided to always pass -Dfwctl=enabled -Dkeyutils=enabled
in Buildroot.
Finally, since docker services are currently unavailable in my region,
I did not use test-pkg. Please point out any issues, thank you.
Changes in v2:
- Remove dependency BR2_LINUX_KERNEL, host-meson and host-ninja
- Add BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_16 for __struct_group
- Add invisible comments
- Keep libtracefs optional
- Sort all rows with "select BR2_PACKAGE_" and "_DEPENDENCIES" in alphabetical order
- Update _LICENSE and _LICENSE_FILES
- Add the missing dependency "udev"
- Use $(STAGING_DIR) instead of $(TARGET_DIR)
Chen Pei (2):
package/ndctl: new package
DEVELOPERS: Add Chen Pei to ndctl
DEVELOPERS | 1 +
package/Config.in | 1 +
package/ndctl/Config.in | 25 ++++++++++++++++++++
package/ndctl/ndctl.hash | 7 ++++++
package/ndctl/ndctl.mk | 51 ++++++++++++++++++++++++++++++++++++++++
5 files changed, 85 insertions(+)
create mode 100644 package/ndctl/Config.in
create mode 100644 package/ndctl/ndctl.hash
create mode 100644 package/ndctl/ndctl.mk
--
2.50.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-03-10 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 8:18 cp0613 [this message]
2026-03-10 8:18 ` [Buildroot] [PATCH v2 1/2] package/ndctl: new package cp0613
2026-03-19 20:51 ` Julien Olivain via buildroot
2026-03-27 12:57 ` cp0613
2026-03-27 18:34 ` Julien Olivain via buildroot
2026-03-10 8:18 ` [Buildroot] [PATCH v2 2/2] DEVELOPERS: Add Chen Pei to ndctl cp0613
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=20260310081850.33001-1-cp0613@linux.alibaba.com \
--to=cp0613@linux.alibaba.com \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
/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