From: Stephen Boyd <sboyd@kernel.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH] clk: qcom: adjust selects for SM_VIDEOCC_8150 and SM_VIDEOCC_8250
Date: Sat, 28 Aug 2021 21:00:41 -0700 [thread overview]
Message-ID: <163020964167.2676726.11842390922063654401@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20210816135930.11810-1-lukas.bulwahn@gmail.com>
Quoting Lukas Bulwahn (2021-08-16 06:59:30)
> Commit 5658e8cf1a8a ("clk: qcom: add video clock controller driver for
> SM8150") and commit 0e94711a1f29 ("clk: qcom: add video clock controller
> driver for SM8250") add config SM_VIDEOCC_8150 and config SM_VIDEOCC_8250,
> which select the non-existing configs SDM_GCC_8150 and SDM_GCC_8250,
> respectively.
>
> Hence, ./scripts/checkkconfigsymbols.py warns:
>
> SDM_GCC_8150
> Referencing files: drivers/clk/qcom/Kconfig
>
> SDM_GCC_8250
> Referencing files: drivers/clk/qcom/Kconfig
>
> It is probably just a typo (or naming confusion of using SM_GCC_xxx and
> SDM_GCC_xxx for various Qualcomm clock drivers) in the config definitions
> for config SM_VIDEOCC_8150 and SM_VIDEOCC_8250, and intends to select the
> existing SM_GCC_8150 and SM_GCC_8250, respectively.
>
> Adjust the selects to the existing configs.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
Applied to clk-next
prev parent reply other threads:[~2021-08-29 4:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 13:59 [PATCH] clk: qcom: adjust selects for SM_VIDEOCC_8150 and SM_VIDEOCC_8250 Lukas Bulwahn
2021-08-29 4:00 ` Stephen Boyd [this message]
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=163020964167.2676726.11842390922063654401@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mturquette@baylibre.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: 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).