From: Oliver Graute <oliver.graute@gmail.com>
To: Abel Vesa <abel.vesa@nxp.com>
Cc: "sboyd@kernel.org" <sboyd@kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCHv2] clk: add imx8 clk defines
Date: Thu, 11 Jul 2019 10:57:25 +0200 [thread overview]
Message-ID: <20190711085725.GA1385@optiplex> (raw)
In-Reply-To: <20190711082039.zze4t22rvlgdxzow@fsr-ub1664-175>
On 11/07/19, Abel Vesa wrote:
> On 19-06-19 09:39:52, Oliver Graute wrote:
> > From: Oliver Graute <oliver.graute@kococonnector.com>
> >
> > added header defines for imx8qm clock
> >
> > Signed-off-by: Oliver Graute <oliver.graute@kococonnector.com>
>
> Again, this seems to be taken from some vendor tree, so please keep the
> original author.
yes the header defines is from NXP vendor tree. One of orginal authors is
Author: Anson Huang <Anson.Huang@nxp.com>
Date: Thu Jan 19 03:53:31 2017 +0800
MLK-13911-3 ARM64: dts: imx8qm: add dtsi
Add i.MX8QM dtsi support.
https://github.com/ADVANTECH-Corp/linux-imx6.git
Whats is the right way to attribute him?
Best regards,
Oliver
next prev parent reply other threads:[~2019-07-11 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 7:39 [PATCHv2] clk: add imx8 clk defines Oliver Graute
2019-07-09 20:03 ` Rob Herring
2019-07-11 8:20 ` Abel Vesa
2019-07-11 8:57 ` Oliver Graute [this message]
2019-07-11 10:09 ` Daniel Baluta
-- strict thread matches above, loose matches on Subject: below --
2019-06-19 7:34 Oliver Graute
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=20190711085725.GA1385@optiplex \
--to=oliver.graute@gmail.com \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.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).