>>> Prefer informative messages rather than none with ABORT_ON. Document >>> one failure mode and add an error message for another. >> >> Does such a wording really fit to the known requirement “Solve only one problem per patch.”? >> >> See also: >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.4#n81 > > Sorry your explanation isn't clear. Do you really find the application of the linked development documentation unclear in this case? > Sorry your explanation isn't clear. Please can you elaborate. Will it become helpful to split the proposed patch into smaller update steps? Regards, Markus
