Hi Julian, > On 6/11/26 17:21, Yunseong Kim wrote: >> +config KCOV_DATAFLOW_RET >> + bool "Enable KCOV dataflow: return value capture" >> + depends on KCOV >> + depends on DEBUG_INFO >> + depends on $(cc-option,-fsanitize-coverage=trace-ret) >> + help >> + Captures function return values via /sys/kernel/debug/kcov_dataflow. >> + Struct pointer returns are auto-expanded using compiler DebugInfo >> + metadata, recording individual field values at runtime. >> + Enable per-module with: KCOV_DATAFLOW_file.o := y in the Makefile. >> + Requires clang with -fsanitize-coverage=trace-ret support. >> + >> +config KCOV_DATAFLOW_NO_INLINE >> + bool "Disable inlining for dataflow-instrumented files" >> + default n > In Kconfig, when you don't specify any default explicitly, it's > implicitly 'default n'. > > I think either style (implicit or explicit) is fine and both are used > throughout the kernel, but is there any reason to make it explicit only > for KCOV_DATAFLOW_NO_INLINE, and implicit for the others?
Thank you for pointing out. You're right, there's no reason to make it explicit only for this one. I'll drop the "default n" line to be consistent with the other options in the same block. > - Julian Braha Best regards, Yunseong
