From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Taniya Das <tdas@codeaurora.org>
Cc: David Brown <david.brown@linaro.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, robh@kernel.org, robh+dt@kernel.org,
Taniya Das <tdas@codeaurora.org>
Subject: Re: [PATCH v1 2/3] dt-bindings: clock: Introduce QCOM Display clock bindings
Date: Mon, 23 Dec 2019 18:38:27 -0800 [thread overview]
Message-ID: <20191224023827.D9A312070E@mail.kernel.org> (raw)
In-Reply-To: <1573812245-23827-3-git-send-email-tdas@codeaurora.org>
Quoting Taniya Das (2019-11-15 02:04:04)
> Add device tree bindings for display clock controller for
> Qualcomm Technology Inc's SC7180 SoCs.
>
> Signed-off-by: Taniya Das <tdas@codeaurora.org>
> ---
Applied to clk-next
next prev parent reply other threads:[~2019-12-24 2:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 10:04 [PATCH v1 0/3] Add display clock controller driver for SC7180 Taniya Das
2019-11-15 10:04 ` [PATCH v1 1/3] dt-bindings: clock: Add YAML schemas for the QCOM DISPCC clock bindings Taniya Das
2019-12-03 17:17 ` Rob Herring
2019-12-24 2:38 ` Stephen Boyd
2019-11-15 10:04 ` [PATCH v1 2/3] dt-bindings: clock: Introduce QCOM Display " Taniya Das
2019-12-03 17:19 ` Rob Herring
2019-12-24 2:38 ` Stephen Boyd [this message]
2019-11-15 10:04 ` [PATCH v1 3/3] clk: qcom: Add display clock controller driver for SC7180 Taniya Das
2019-12-24 2:38 ` Stephen Boyd
-- strict thread matches above, loose matches on Subject: below --
2019-11-15 9:58 [PATCH v1 0/3] " Taniya Das
2019-11-15 9:58 ` [PATCH v1 2/3] dt-bindings: clock: Introduce QCOM Display clock bindings Taniya Das
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=20191224023827.D9A312070E@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tdas@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).