From: Nathan Chancellor <nathan@kernel.org>
To: sboyd@kernel.org, andersson@kernel.org
Cc: konrad.dybcio@linaro.org, mturquette@baylibre.com,
bryan.odonoghue@linaro.org, neil.armstrong@linaro.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
patches@lists.linux.dev, Nathan Chancellor <nathan@kernel.org>
Subject: [PATCH 0/2] clk: qcom: Fix two driver Kconfig dependencies
Date: Mon, 18 Mar 2024 08:18:09 -0700 [thread overview]
Message-ID: <20240318-fix-some-qcom-kconfig-deps-v1-0-ea0773e3df5a@kernel.org> (raw)
This series fixes two Kconfig warnings that I recently saw crop up in my
build tests because the dependencies for newly added drivers in 6.8 are
not correct.
This is now the fourth set of changes to avoid warnings of this nature
for the exact same reason... is there anything that can be done to
ensure this does not continue to happen? See
b6bcd1c0c27e ("clk: qcom: fix some Kconfig corner cases")
75d1d3a433f0 ("clk: qcom: Fix SM_GPUCC_8450 dependencies")
e8d66d02defd ("clk: qcom: Fix SM_CAMCC_8550 dependencies")
---
Nathan Chancellor (2):
clk: qcom: Fix SC_CAMCC_8280XP dependencies
clk: qcom: Fix SM_GPUCC_8650 dependencies
drivers/clk/qcom/Kconfig | 2 ++
1 file changed, 2 insertions(+)
---
base-commit: 3066c521be9db14964d78c6c431c97a424468ded
change-id: 20240318-fix-some-qcom-kconfig-deps-cc9be94f63ba
Best regards,
--
Nathan Chancellor <nathan@kernel.org>
next reply other threads:[~2024-03-18 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 15:18 Nathan Chancellor [this message]
2024-03-18 15:18 ` [PATCH 1/2] clk: qcom: Fix SC_CAMCC_8280XP dependencies Nathan Chancellor
2024-03-18 15:21 ` Dmitry Baryshkov
2024-03-18 15:18 ` [PATCH 2/2] clk: qcom: Fix SM_GPUCC_8650 dependencies Nathan Chancellor
2024-03-18 15:21 ` Dmitry Baryshkov
2024-04-21 22:29 ` [PATCH 0/2] clk: qcom: Fix two driver Kconfig dependencies Bjorn Andersson
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=20240318-fix-some-qcom-kconfig-deps-v1-0-ea0773e3df5a@kernel.org \
--to=nathan@kernel.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=patches@lists.linux.dev \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).