From: Stephen Boyd <sboyd@kernel.org>
To: agross@kernel.org, devicetree@vger.kernel.org,
linus.walleij@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-soc@vger.kernel.org, robh+dt@kernel.org,
sivaprak@codeaurora.org, sricharan@codeaurora.org
Cc: Anusha Canchi Ramachandra Rao <anusharao@codeaurora.org>,
Abhishek Sahu <absahu@codeaurora.org>
Subject: Re: [PATCH V2 2/2] clk: qcom: Add ipq6018 Global Clock Controller support
Date: Thu, 09 Jan 2020 16:11:38 -0800 [thread overview]
Message-ID: <20200110001138.BEB1C20848@mail.kernel.org> (raw)
In-Reply-To: <1578557121-423-3-git-send-email-sricharan@codeaurora.org>
Quoting Sricharan R (2020-01-09 00:05:21)
> This patch adds support for the global clock controller found on
> the ipq6018 based devices.
>
> Also fixed the sparse warnings reported by,
> Reported-by: kbuild test robot <lkp@intel.com>
> Co-developed-by: Anusha Canchi Ramachandra Rao <anusharao@codeaurora.org>
> Signed-off-by: Anusha Canchi Ramachandra Rao <anusharao@codeaurora.org>
> Co-developed-by: Abhishek Sahu <absahu@codeaurora.org>
> Signed-off-by: Abhishek Sahu <absahu@codeaurora.org>
> Co-developed-by: Sivaprakash Murugesan <sivaprak@codeaurora.org>
> Signed-off-by: Sivaprakash Murugesan <sivaprak@codeaurora.org>
> Signed-off-by: Sricharan R <sricharan@codeaurora.org>
> ---
Applied to clk-next
prev parent reply other threads:[~2020-01-10 0:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 8:05 [PATCH V2 0/2] Add Global clock controller support for IPQ6018 Sricharan R
2020-01-09 8:05 ` [PATCH V2 1/2] clk: qcom: Add DT bindings for ipq6018 gcc clock controller Sricharan R
2020-01-10 0:11 ` Stephen Boyd
[not found] ` <1578557121-423-3-git-send-email-sricharan@codeaurora.org>
2020-01-10 0:11 ` 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=20200110001138.BEB1C20848@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=absahu@codeaurora.org \
--cc=agross@kernel.org \
--cc=anusharao@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sivaprak@codeaurora.org \
--cc=sricharan@codeaurora.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).