From: Jiabing Wan <wanjiabing@vivo.com> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, Vinod Koul <vkoul@kernel.org>, Orson Zhai <orsonzhai@gmail.com>, Baolin Wang <baolin.wang7@gmail.com>, Chunyan Zhang <zhang.lyra@gmail.com>, Linus Walleij <linus.walleij@linaro.org>, dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 2/4] dmaengine: sprd-dma: Remove unneeded ERROR check before clk_disable_unprepare Date: Wed, 18 May 2022 10:44:05 +0800 [thread overview] Message-ID: <b0438374-ff82-e74f-0b83-e0f2b4a99e36@vivo.com> (raw) In-Reply-To: <214de163-d576-d9be-76f2-3b70eefd6e68@linaro.org> Hi, On 2022/5/17 23:13, Krzysztof Kozlowski wrote: > On 16/05/2022 10:41, Wan Jiabing wrote: >> clk_disable_unprepare() already checks ERROR by using IS_ERR_OR_NULL. > Hmm, maybe I am looking at different sources, but which commit > introduced IS_ERR_OR_NULL() check? Where is it in the sources? > In commit 4dff95dc9477a, IS_ERR_OR_NULL check is added in clk_disable() and clk_unprepare(). And clk_disable_unprepare() just calls clk_disable() and clk_unprepare(): static inline void clk_disable_unprepare(struct clk *clk) { clk_disable(clk); clk_unprepare(clk); } > > Best regards, > Krzysztof Thanks, Wan Jiabing
WARNING: multiple messages have this Message-ID (diff)
From: Jiabing Wan <wanjiabing@vivo.com> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, Vinod Koul <vkoul@kernel.org>, Orson Zhai <orsonzhai@gmail.com>, Baolin Wang <baolin.wang7@gmail.com>, Chunyan Zhang <zhang.lyra@gmail.com>, Linus Walleij <linus.walleij@linaro.org>, dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 2/4] dmaengine: sprd-dma: Remove unneeded ERROR check before clk_disable_unprepare Date: Wed, 18 May 2022 10:44:05 +0800 [thread overview] Message-ID: <b0438374-ff82-e74f-0b83-e0f2b4a99e36@vivo.com> (raw) In-Reply-To: <214de163-d576-d9be-76f2-3b70eefd6e68@linaro.org> Hi, On 2022/5/17 23:13, Krzysztof Kozlowski wrote: > On 16/05/2022 10:41, Wan Jiabing wrote: >> clk_disable_unprepare() already checks ERROR by using IS_ERR_OR_NULL. > Hmm, maybe I am looking at different sources, but which commit > introduced IS_ERR_OR_NULL() check? Where is it in the sources? > In commit 4dff95dc9477a, IS_ERR_OR_NULL check is added in clk_disable() and clk_unprepare(). And clk_disable_unprepare() just calls clk_disable() and clk_unprepare(): static inline void clk_disable_unprepare(struct clk *clk) { clk_disable(clk); clk_unprepare(clk); } > > Best regards, > Krzysztof Thanks, Wan Jiabing _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-18 2:44 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-16 8:41 [PATCH 0/4] dmaengine: Remove unneeded ERROR checks before clk_xxx Wan Jiabing 2022-05-16 8:41 ` Wan Jiabing 2022-05-16 8:41 ` [PATCH 1/4] dmaengine: ep93xx_dma: Remove unneeded ERROR check before clk_put Wan Jiabing 2022-05-16 8:41 ` Wan Jiabing 2022-05-18 7:12 ` Krzysztof Kozlowski 2022-05-18 7:12 ` Krzysztof Kozlowski 2022-05-16 8:41 ` [PATCH 2/4] dmaengine: sprd-dma: Remove unneeded ERROR check before clk_disable_unprepare Wan Jiabing 2022-05-16 8:41 ` Wan Jiabing 2022-05-17 15:13 ` Krzysztof Kozlowski 2022-05-17 15:13 ` Krzysztof Kozlowski 2022-05-18 2:44 ` Jiabing Wan [this message] 2022-05-18 2:44 ` Jiabing Wan 2022-05-18 7:10 ` Krzysztof Kozlowski 2022-05-18 7:10 ` Krzysztof Kozlowski 2022-05-18 7:12 ` Krzysztof Kozlowski 2022-05-18 7:12 ` Krzysztof Kozlowski 2022-05-16 8:41 ` [PATCH 3/4] dmaengine: ste_dma40: Remove unneeded ERROR and NULL check in ste_dma40 Wan Jiabing 2022-05-16 8:41 ` Wan Jiabing 2022-05-18 7:15 ` Krzysztof Kozlowski 2022-05-18 7:15 ` Krzysztof Kozlowski 2022-05-19 6:34 ` Jiabing Wan 2022-05-19 6:34 ` Jiabing Wan 2022-05-16 8:41 ` [PATCH 4/4] dmaengine: xgene-dma: Remove unneeded ERROR check before clk_disable_unprepare Wan Jiabing 2022-05-16 8:41 ` Wan Jiabing
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=b0438374-ff82-e74f-0b83-e0f2b4a99e36@vivo.com \ --to=wanjiabing@vivo.com \ --cc=baolin.wang7@gmail.com \ --cc=dmaengine@vger.kernel.org \ --cc=krzysztof.kozlowski@linaro.org \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=orsonzhai@gmail.com \ --cc=vkoul@kernel.org \ --cc=zhang.lyra@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.