summaryrefslogtreecommitdiff
path: root/drivers/pcmcia
diff options
context:
space:
mode:
authorDan Williams <dan.j.williams@intel.com>2023-12-07 04:59:38 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-12-15 19:07:12 +0300
commitfddd9e3e4e716e3c484413b95579b40a7b6dbe41 (patch)
tree80b08197e200cc90e8e8e9843b095aef95edceb1 /drivers/pcmcia
parentce8df3f4d0d99ee2f76d1260fe69793ad05a13bf (diff)
downloadlinux-fddd9e3e4e716e3c484413b95579b40a7b6dbe41.tar.xz
tools/testing/nvdimm: Add compile-test coverage for ndtest
Greg lamented: "Ick, sorry about that, obviously this test isn't actually built by any bots :(" A quick and dirty way to prevent this problem going forward is to always compile ndtest.ko whenever nfit_test is built. While this still does not expose the test code to any of the known build bots, it at least makes it the case that anyone that runs the x86 tests also compiles the powerpc test. I.e. the Intel NVDIMM maintainers are less likely to fall into this hole in the future. Link: http://lore.kernel.org/r/2023112729-aids-drainable-5744@gregkh Cc: Greg KH <gregkh@linuxfoundation.org> Cc: Yi Zhang <yi.zhang@redhat.com> Cc: Dave Jiang <dave.jiang@intel.com> Cc: Ira Weiny <ira.weiny@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> Reviewed-by: Ira Weiny <ira.weiny@intel.com> Reviewed-by: Dave Jiang <dave.jiang@intel.com> Link: https://lore.kernel.org/r/170191437889.426826.15528612879942432918.stgit@dwillia2-xfh.jf.intel.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/pcmcia')
0 files changed, 0 insertions, 0 deletions