From: Bjorn Andersson <andersson@kernel.org>
To: sboyd@kernel.org, Nathan Chancellor <nathan@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
Subject: Re: [PATCH 0/2] clk: qcom: Fix two driver Kconfig dependencies
Date: Sun, 21 Apr 2024 17:29:20 -0500 [thread overview]
Message-ID: <171373856767.1196479.14241619358074535915.b4-ty@kernel.org> (raw)
In-Reply-To: <20240318-fix-some-qcom-kconfig-deps-v1-0-ea0773e3df5a@kernel.org>
On Mon, 18 Mar 2024 08:18:09 -0700, Nathan Chancellor wrote:
> 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
>
> [...]
Applied, thanks!
[1/2] clk: qcom: Fix SC_CAMCC_8280XP dependencies
commit: 0e79d702bf7fac2e63fc32a1b4ff307d71db692f
[2/2] clk: qcom: Fix SM_GPUCC_8650 dependencies
commit: 551eb5194bf328652decc5531edd9c65a5d2a17c
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-04-21 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 15:18 [PATCH 0/2] clk: qcom: Fix two driver Kconfig dependencies Nathan Chancellor
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 ` Bjorn Andersson [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=171373856767.1196479.14241619358074535915.b4-ty@kernel.org \
--to=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=nathan@kernel.org \
--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).