linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Georgi Djakov <georgi.djakov@linaro.org>
To: Konrad Dybcio <konrad.dybcio@somainline.org>,
	AngeloGioacchino Del Regno <kholk11@gmail.com>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
	marijns95@gmail.com, martin.botka1@gmail.com,
	MSM <linux-arm-msm@vger.kernel.org>,
	phone-devel@vger.kernel.org,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	linux-pm@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] interconnect: qcom: Add SDM660 interconnect provider driver
Date: Tue, 9 Feb 2021 12:53:17 +0200	[thread overview]
Message-ID: <d25e4301-a2b5-e212-9c88-a4c66936f4ee@linaro.org> (raw)
In-Reply-To: <55f89461-607a-8864-ff31-77d16448128c@somainline.org>

On 9.02.21 0:09, Konrad Dybcio wrote:
> MMCC got merged via the clk-next tree, so.. since this driver was
> technically in, say for the dt-bindings conflict.. can we get it
> merged again? :)

Thanks for the update! I'll take it for v5.13.

Cheers,
Georgi

      reply	other threads:[~2021-02-09 10:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-17 13:37 [PATCH v4 0/2] Add SDM630/636/660 interconnect driver kholk11
2020-10-17 13:37 ` [PATCH v4 1/2] dt-bindings: interconnect: Add bindings for Qualcomm SDM660 NoC kholk11
2020-10-19 19:56   ` Rob Herring
2020-10-19 19:58   ` Rob Herring
2020-10-19 20:44     ` Martin Botka
2020-11-30 14:29       ` Rob Herring
2020-11-30 14:52         ` Georgi Djakov
2020-10-17 13:37 ` [PATCH v4 2/2] interconnect: qcom: Add SDM660 interconnect provider driver kholk11
2020-11-03 16:24   ` Georgi Djakov
2020-12-04 18:06     ` AngeloGioacchino Del Regno
2021-02-08 22:09       ` Konrad Dybcio
2021-02-09 10:53         ` Georgi Djakov [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=d25e4301-a2b5-e212-9c88-a4c66936f4ee@linaro.org \
    --to=georgi.djakov@linaro.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kholk11@gmail.com \
    --cc=konrad.dybcio@somainline.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=marijns95@gmail.com \
    --cc=martin.botka1@gmail.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh+dt@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 NNTP newsgroup(s).