Jeff Johnson <quic_jjohnson@xxxxxxxxxxx> writes: >>>> + default: >>>> + ath12k_err(ab, "invalid descriptor type %d in cmem init\n", type); >>>> + return; >>>> + } >>>> + >>>> + /* Write to PPT in CMEM */ >>>> + for (i = start; i < end; i++) >>>> + ath12k_hif_write32(ab, cmem_base + ATH12K_PPT_ADDR_OFFSET(i), >>>> + dp->spt_info[i].paddr >> ATH12K_SPT_4K_ALIGN_OFFSET); >>>> +} >>> >>> Here's a good example why I don't like functions returning void. How do >>> we handle the errors in this case? >>> >> >> sure, will handle the error case in the caller. >> > > this is a static function with one caller. the only error is the default case > which will never be hit. adding logic to return an error and then check it in > the caller seems like overkill. why not just WARN() in the default case since > this would be a logic error with newly added code? I think the software will be more robust then all errors are properly handled in a uniform way. For example, will everyone notice the warning message? What if the function is extended later and then the person doesn't add any error handling "because it didn't have that even earlier"? It's also a lot easier to review if error handling follows the same style throughout the driver. I didn't do any measurements but the overhead from this shouldn't be that large, maybe few bytes in the binary and few new lines in the source code. I think that's a reasonable price to pay from having more robust software. This is why I want to avoid void functions as much as possible. Of course there also are good cases when to use void functions, like here: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=ath-next&id=6ef5b4c9598c928b3e2c4c4b543c81331941f136 -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
