jchu314

@djbw The "kernel BUG at mm/page_alloc.c" issue was seen when running the above script in two separate terminals simultaneously. You're correct, that was a different issue which I can confirm...

Thanks Dan for the prompt response. There seems to be another issue. build/rhel/ndctl.spec has `Version: 72.22.g351badd+` but `$ git describe v72-22-g351badd` and `$ ./git-version 72.22.g351badd.dirty ` so, "./rpmbuild.sh build/rhel/ndctl.spec" complains...

I guess 'dirty' means '+', it's just a matter of consistency.

Oh, I see. I changed the meson_option file to elect 'asciidoc' instead of the default 'asciidoctor', guess I could do that via meson configure. Thanks!

Dan, `./rpmbuild.sh build/rhel/ndctl.spec` complains `RPM build errors: File not found: /root/rpmbuild/BUILDROOT/ndctl-72.22.g351badd-1.el8.x86_64/usr/lib/systemd/system/ndctl-monitor.service` It appears that the `$(repo_dir)/ndctl/ndctl-monitor.service` was not copied over to `$(repo_dir)/build/`, and so isn't installed by ` sudo meson...

seen above as well. The issue: 1) "echo $?" returns 0 could confuse automated test scripts, 2) conflict error message: "failed to enable" versus "enabled 1 region", which is what's...

Hmm, any one? Does it make sense to update the udev rule such that "load-keys" is run only if a master exists somewhere? Thanks!