From: matthew.gerlach@linux.intel.com
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: dinguyen@kernel.org, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org
Subject: Re: [PATCH v4 1/3] dt-bindings: soc: add bindings for Intel HPS Copy Engine
Date: Tue, 10 May 2022 07:16:56 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2205100715570.612063@rhweight-WRK1> (raw)
In-Reply-To: <e14122b9-cd7a-b2a9-93a5-cde6139969c1@linaro.org>
On Mon, 9 May 2022, Krzysztof Kozlowski wrote:
> On 08/05/2022 16:26, matthew.gerlach@linux.intel.com wrote:
>> From: Matthew Gerlach <matthew.gerlach@linux.intel.com>
>>
>> Add device tree bindings documentation for the Intel Hard
>> Processor System (HPS) Copy Engine.
>>
>> Signed-off-by: Matthew Gerlach <matthew.gerlach@linux.intel.com>
>
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Hi Krzysztof,
Thank you for the review. I will add your tag and submit a v5 patchset.
Matthew
>
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2022-05-10 14:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 14:26 [PATCH v4 0/3] Add device tree for Intel n6000 matthew.gerlach
2022-05-08 14:26 ` [PATCH v4 1/3] dt-bindings: soc: add bindings for Intel HPS Copy Engine matthew.gerlach
2022-05-09 7:22 ` Krzysztof Kozlowski
2022-05-10 14:16 ` matthew.gerlach [this message]
2022-05-10 19:15 ` Rob Herring
2022-05-10 22:23 ` matthew.gerlach
2022-05-18 15:00 ` Rob Herring
2022-05-10 19:17 ` Rob Herring
2022-05-10 22:26 ` matthew.gerlach
2022-05-08 14:26 ` [PATCH v4 2/3] dt-bindings: intel: add binding for Intel n6000 matthew.gerlach
2022-05-08 14:26 ` [PATCH v4 3/3] arm64: dts: intel: add device tree for n6000 matthew.gerlach
2022-05-09 7:23 ` Krzysztof Kozlowski
2022-05-10 14:17 ` matthew.gerlach
2022-05-10 19:22 ` Rob Herring
2022-05-10 22:28 ` matthew.gerlach
2022-05-12 14:41 ` [PATCH v4 0/3] Add device tree for Intel n6000 Dinh Nguyen
2022-05-12 15:18 ` matthew.gerlach
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=alpine.DEB.2.22.394.2205100715570.612063@rhweight-WRK1 \
--to=matthew.gerlach@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®