[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA+D8APR2NGAn9jRDSZzr1fgj5u0hAvH19VxZS+tj2A7j3PCuw@mail.gmail.com>
Date: Tue, 23 Jun 2020 16:32:02 +0800
From: Shengjiu Wang <shengjiu.wang@...il.com>
To: Markus Elfring <Markus.Elfring@....de>
Cc: Shengjiu Wang <shengjiu.wang@....com>,
Linux-ALSA <alsa-devel@...a-project.org>,
linuxppc-dev@...ts.ozlabs.org, Timur Tabi <timur@...nel.org>,
Xiubo Li <Xiubo.Lee@...il.com>, Takashi Iwai <tiwai@...e.com>,
kernel-janitors@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
Nicolin Chen <nicoleotsuka@...il.com>,
Mark Brown <broonie@...nel.org>,
Fabio Estevam <festevam@...il.com>
Subject: Re: [PATCH v2 1/2] ASoC: fsl_mqs: Don't check clock is NULL before
calling clk API
On Tue, Jun 23, 2020 at 3:38 PM Markus Elfring <Markus.Elfring@....de> wrote:
>
> > In-Reply-To: <cover.1592888591.git.shengjiu.wang@....com>
>
> 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
Powered by blists - more mailing lists