From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shengjiu Wang Date: Tue, 23 Jun 2020 08:32:02 +0000 Subject: Re: [PATCH v2 1/2] ASoC: fsl_mqs: Don't check clock is NULL before calling clk API Message-Id: List-Id: References: <39ac8f24-3148-2a3d-3f8d-91567b3c4c9e@web.de> In-Reply-To: <39ac8f24-3148-2a3d-3f8d-91567b3c4c9e@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Markus Elfring Cc: Linux-ALSA , Timur Tabi , Xiubo Li , Fabio Estevam , Shengjiu Wang , kernel-janitors@vger.kernel.org, Takashi Iwai , linux-kernel , Nicolin Chen , Mark Brown , linuxppc-dev@lists.ozlabs.org On Tue, Jun 23, 2020 at 3:38 PM Markus Elfring wrote: > > > In-Reply-To: > > I guess that it should be sufficient to specify such a field once > for the header information. seems it's caused by my "git format-patch" command, I will update it, hope it is better next time. > > > > Because clk_prepare_enable and clk_disable_unprepare should > > check input clock parameter is NULL or not internally, > > I find this change description unclear. clk_prepare_enable and clk_disable_unprepare check the input clock parameter in the beginning of the function, if the parameter is NULL, clk_prepare_enable and clk_disable_unprepare will return immediately. So Don't need to check input clock parameters before calling clk API. Do you think this commit message is better? best regards wang shengjiu