On Sat, 15 Jan 2022 17:24:57 -0500, Sean Anderson wrote:
clk_free cleans up resources allocated by clk_request et. al. It returns an error code, but it really shouldn't. Much like regular free(), there is typically no way to handle an error, and errors from clk_free shouldn't prevent progress in the rest of the program. Make clk_free (and rfree) return void.
Sean Anderson (7): clk: Make rfree return void dma: bcm6348: Don't check clk_free net: bcm63xx: Don't check clk_free phy: bcm63xx: Don't check clk_free spi: bcm63xx: Don't check clk_free spi: dw: Don't check clk_free clk: Make clk_free return void
[...]
Applied, thanks!
[1/7] clk: Make rfree return void commit: 276d446757e462c210768eb0bbd48450ae254f51 [2/7] dma: bcm6348: Don't check clk_free commit: 454af567edc0b02842c83aaf1a60bbcb766af0cd [3/7] net: bcm63xx: Don't check clk_free commit: b2e0889abacfd453131359156fe279996727d95b [4/7] phy: bcm63xx: Don't check clk_free commit: ad20358c7462159d5f9012facba9dec1e197aaca [5/7] spi: bcm63xx: Don't check clk_free commit: dfdb227c3d018983f37cc97fe003e231a81a46ea [6/7] spi: dw: Don't check clk_free commit: 3cbdd4cab951b8bd3f2e76066e6911f9780c4eb1 [7/7] clk: Make clk_free return void commit: ac15e789caecec19d29ee9c5869305d3c3ddfb42
Best regards,