From: Stephen Boyd <sboyd@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Vinod Koul <vkoul@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
Andy Gross <agross@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/8] clk: qcom: gcc-sm6350: explicitly include clk-provider.h
Date: Wed, 15 Dec 2021 16:45:40 -0800 [thread overview]
Message-ID: <20211216004541.60B90C36AE1@smtp.kernel.org> (raw)
In-Reply-To: <20211215113803.620032-4-vkoul@kernel.org>
Quoting Vinod Koul (2021-12-15 03:37:58)
> Per Stephen, clk providers need to include clk-provider.h, so include in
> this driver as well
>
> Signed-off-by: Vinod Koul <vkoul@kernel.org>
> ---
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
next prev parent reply other threads:[~2021-12-16 0:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 11:37 [PATCH 0/8] clk: qcom: explicitly include clk-provider.h Vinod Koul
2021-12-15 11:37 ` [PATCH 1/8] clk: qcom: gcc-sm8350: " Vinod Koul
2021-12-16 0:45 ` Stephen Boyd
2021-12-15 11:37 ` [PATCH 2/8] clk: qcom: gcc-msm8994: " Vinod Koul
2021-12-16 0:45 ` Stephen Boyd
2021-12-15 11:37 ` [PATCH 3/8] clk: qcom: gcc-sm6350: " Vinod Koul
2021-12-16 0:45 ` Stephen Boyd [this message]
2021-12-15 11:37 ` [PATCH 4/8] clk: qcom: lpasscc-sc7280: " Vinod Koul
2021-12-16 0:45 ` Stephen Boyd
2021-12-15 11:38 ` [PATCH 5/8] clk: qcom: lpasscc-sdm845: " Vinod Koul
2021-12-16 0:46 ` Stephen Boyd
2021-12-15 11:38 ` [PATCH 6/8] clk: qcom: mmcc-apq8084: " Vinod Koul
2021-12-16 0:46 ` Stephen Boyd
2021-12-15 11:38 ` [PATCH 7/8] clk: qcom: q6sstop-qcs404: " Vinod Koul
2021-12-16 0:46 ` Stephen Boyd
2021-12-15 11:38 ` [PATCH 8/8] clk: qcom: turingcc-qcs404: " Vinod Koul
2021-12-16 0:46 ` Stephen Boyd
2021-12-21 5:21 ` [PATCH 0/8] clk: qcom: " 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=20211216004541.60B90C36AE1@smtp.kernel.org \
--to=sboyd@kernel.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=mturquette@baylibre.com \
--cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.