linux-next: build failure after merge of the device-mapper tree
Hi all,
After merging the device-mapper tree, today's linux-next build (powerpc ppc64_defconfig) failed like this:
drivers/md/dm-linear.c:234:3: error: 'struct target_type' has no member named 'report_zones'
234 | .report_zones = linear_report_zones,
| ^~~~~~~~~~~~
drivers/md/dm-crypt.c:3585:3: error: 'struct target_type' has no member named 'report_zones'
3585 | .report_zones = crypt_report_zones,
| ^~~~~~~~~~~~Caused by commit
7defd0da9dd2 ("dm: simplify target code conditional on CONFIG_BLK_DEV_ZONED")
The report_zones members existence is guarded by CONFIG_BLK_DEV_ZONED.
I have used the device-mapper tree from next-20210210 for today.
Signature · 2 lines
Cheers, Stephen Rothwell
Quoted 12 lines · Stephen Rothwell
Hi all,
After merging the device-mapper tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/md/dm-linear.c:234:3: error: 'structtarget_type' has no member named 'report_zones'
234 | .report_zones =linear_report_zones,| ^~~~~~~~~~~~ drivers/md/dm-crypt.c:3585:3: error: 'struct target_type' has no member named 'report_zones' 3585 | .report_zones = crypt_report_zones, | ^~~~~~~~~~~~
Quoted 7 lines
Caused by commit
7defd0da9dd2("dm: simplify target code conditional onCONFIG_BLK_DEV_ZONED")The
report_zonesmembers existence is guarded byCONFIG_BLK_DEV_ZONED.I have used the device-mapper tree from next-20210210 for today.
Sorry, I didn't test with CONFIG_BLK_DEV_ZONED disabled, now fixed.
Thanks,
Mike