devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konradybcio@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	linux-clk@vger.kernel.org, DTML <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] Add compatible strings and the include files for the msm8992 GCC.
Date: Wed, 10 Jun 2020 00:43:19 +0200	[thread overview]
Message-ID: <CAMS8qEVZuGh-hkUQDoC0avSb7gKkWE7cswvhXHZHJhDPPU5u+Q@mail.gmail.com> (raw)
In-Reply-To: <20200609221917.GA1595469@bogus>

>'dt-bindings: clock: qcom,gcc: ...' for the subject.
Will do.

>Don't care about DT on non-GPL OSs?
I'm not sure I understand? Now that I look at it the copyright to TLF
looks kinda out of place.. what should it be?

>License?
Derp. Will correct in v2.


Thanks for your review
Konrad

  reply	other threads:[~2020-06-09 22:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-31 17:46 [PATCH 0/4] Add msm8992 GCC driver Konrad Dybcio
2020-05-31 17:46 ` [PATCH 1/4] drivers: clk: qcom: " Konrad Dybcio
2020-06-02 23:33   ` Bryan O'Donoghue
2020-05-31 17:46 ` [PATCH 2/4] Add compatible strings and the include files for the msm8992 GCC Konrad Dybcio
2020-06-09 22:19   ` Rob Herring
2020-06-09 22:43     ` Konrad Dybcio [this message]
2020-05-31 17:46 ` [PATCH 3/4] arm64: dts: Adjust msm8992 DTS to use the correct GCC driver Konrad Dybcio
2020-05-31 17:46 ` [PATCH 4/4] driver: clk: Add msm8992 GCC Kconfig and Makefile entries Konrad Dybcio
2020-05-31 17:50   ` Randy Dunlap
2020-05-31 19:48     ` Stephen Boyd

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=CAMS8qEVZuGh-hkUQDoC0avSb7gKkWE7cswvhXHZHJhDPPU5u+Q@mail.gmail.com \
    --to=konradybcio@gmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@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=mturquette@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --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 NNTP newsgroup(s).