From: Dinh Nguyen <dinguyen@kernel.org>
To: matthew.gerlach@linux.intel.com, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org
Subject: Re: [PATCH v6 0/3] Add device tree for Intel n6000
Date: Sun, 22 May 2022 11:18:40 -0500 [thread overview]
Message-ID: <9d13e27e-4b51-eaa1-81af-20851d3a9fe4@kernel.org> (raw)
In-Reply-To: <20220520143208.1160506-1-matthew.gerlach@linux.intel.com>
Hi Matthew,
On 5/20/22 09:32, matthew.gerlach@linux.intel.com wrote:
> From: Matthew Gerlach <matthew.gerlach@linux.intel.com>
>
> This patch set adds a device tree for the Hard Processor System (HPS)
> on an Agilex based Intel n6000 board.
>
> Patch 1 defines the device tree binding for the HPS Copy Engine IP
> used to copy a bootable image from host memory to HPS DDR.
>
> Patch 2 defines the binding for the Intel n6000 board itself.
>
> Patch 3 adds the device tree for the n6000 board.
>
> Changelog v5 -> v6:
> - move copy engine binding from soc/intel to dma directory
> - remove unnecessary parent device tree node from copy engine example
>
I didn't see any pending comments for V5 so I've already queued it up
for V5.19.
You can make this change in -rc if you want.
Dinh
prev parent reply other threads:[~2022-05-22 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 14:32 [PATCH v6 0/3] Add device tree for Intel n6000 matthew.gerlach
2022-05-20 14:32 ` [PATCH v6 1/3] dt-bindings: soc: add bindings for Intel HPS Copy Engine matthew.gerlach
2022-05-20 14:32 ` [PATCH v6 2/3] dt-bindings: intel: add binding for Intel n6000 matthew.gerlach
2022-05-20 14:32 ` [PATCH v6 3/3] arm64: dts: intel: add device tree for n6000 matthew.gerlach
2022-05-22 16:18 ` Dinh Nguyen [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=9d13e27e-4b51-eaa1-81af-20851d3a9fe4@kernel.org \
--to=dinguyen@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--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).