linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Stephen Boyd <sboyd@kernel.org>, Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH 1/8] clk: qcom: alpha-pll: correct kerneldoc
Date: Thu, 19 May 2022 09:23:06 +0200	[thread overview]
Message-ID: <07c8cac0-ab85-19a7-de2c-14f6dc1c496a@linaro.org> (raw)
In-Reply-To: <20220519001438.E534DC385A9@smtp.kernel.org>

On 19/05/2022 02:14, Stephen Boyd wrote:
> Quoting Krzysztof Kozlowski (2022-05-17 09:46:49)
>> On 01/05/2022 12:35, Krzysztof Kozlowski wrote:
>>> Correct kerneldoc warning:
>>>
>>>   drivers/clk/qcom/clk-alpha-pll.c:1450:
>>>     warning: expecting prototype for clk_lucid_pll_configure(). Prototype was for clk_trion_pll_configure() instead
>>>
>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>
>> Any comments on entire set?
> 
> Please send a cover letter next time. Also they're simply "qcom" related
> but otherwise I'm not sure why they aren't sent to individual subsystem
> lists. They don't depend on each other to build, right?

Indeed, they can go via separate subsystems. I'll split the series in v2.

Best regards,
Krzysztof

  reply	other threads:[~2022-05-19  7:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 10:35 [PATCH 1/8] clk: qcom: alpha-pll: correct kerneldoc Krzysztof Kozlowski
2022-05-01 10:35 ` [PATCH 2/8] firmware: qcom_scm-legacy: " Krzysztof Kozlowski
2022-05-19  0:03   ` Stephen Boyd
2022-05-19  7:20     ` Krzysztof Kozlowski
2022-05-01 10:35 ` [PATCH 3/8] remoteproc: qcom: " Krzysztof Kozlowski
2022-05-19  0:05   ` Stephen Boyd
2022-05-01 10:35 ` [PATCH 4/8] rpmsg: qcom: glink: replace strncpy() with strscpy_pad() Krzysztof Kozlowski
2022-07-18 22:59   ` (subset) " Bjorn Andersson
2022-05-01 10:35 ` [PATCH 5/8] rpmsg: qcom: glink: remove unused name Krzysztof Kozlowski
2022-05-19  0:09   ` Stephen Boyd
2022-05-01 10:35 ` [PATCH 6/8] rpmsg: qcom: correct kerneldoc Krzysztof Kozlowski
2022-05-19  0:11   ` Stephen Boyd
2022-05-01 10:35 ` [PATCH 7/8] soc: qcom: cmd-db: replace strncpy() with strscpy_pad() Krzysztof Kozlowski
2022-05-19  0:12   ` Stephen Boyd
2022-05-01 10:35 ` [PATCH 8/8] soc: qcom: correct kerneldoc Krzysztof Kozlowski
2022-05-19  0:13   ` Stephen Boyd
2022-05-17 16:46 ` [PATCH 1/8] clk: qcom: alpha-pll: " Krzysztof Kozlowski
2022-05-19  0:14   ` Stephen Boyd
2022-05-19  7:23     ` Krzysztof Kozlowski [this message]
2022-05-19  0:02 ` Stephen Boyd
2022-05-19  7:20   ` Krzysztof Kozlowski
2022-05-19  4:30 ` Vladimir Zapolskiy
2022-05-19  7:23   ` Krzysztof Kozlowski

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=07c8cac0-ab85-19a7-de2c-14f6dc1c496a@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).