From: Shawn Guo <shawnguo2@yeah.net>
To: Gilles Talis <gilles.talis@gmail.com>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh@kernel.org,
shawnguo@kernel.org, festevam@gmail.com, alex@voxelbotics.com,
andrew@lunn.ch
Subject: Re: [PATCH v2 0/3] Add support for Emcraft Systems NavQ+ kit
Date: Wed, 3 Apr 2024 09:15:21 +0800 [thread overview]
Message-ID: <ZgytqXy/S63iXbTD@dragon> (raw)
In-Reply-To: <20240330133410.41408-1-gilles.talis@gmail.com>
On Sat, Mar 30, 2024 at 09:34:07AM -0400, Gilles Talis wrote:
> Hello
>
> This series adds a device tree file for the Emcraft Systems NavQ+ kit [1]
>
> The first patch adds a new vendor prefix for Emcraft Systems
> The second one adds the board to the arm/fsl.yaml DT bindings.
> Last patch adds device tree file for the kit.
>
> [1] https://www.emcraft.com/products/1222
>
> Changes in v2:
> - Add Acked-by review tags
> - Fixed device tree warnings reported by dtbs_check
> - Reworked leds node
> - Remove unused i2c6 pinctrl entry
> - Removed unused regulator node in Ethernet entry
> - Link to v1: https://lore.kernel.org/imx/20240328202320.187596-1-gilles.talis@gmail.com/
> ---
> Gilles Talis (3):
> dt-bindings: vendor-prefixes: Add Emcraft Systems
> dt-bindings: arm: Add Emcraft Systems i.MX8M Plus NavQ+ Kit
> arm64: dts: freescale: Add device tree for Emcraft Systems NavQ+ Kit
Applied all, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo2@yeah.net>
To: Gilles Talis <gilles.talis@gmail.com>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh@kernel.org,
shawnguo@kernel.org, festevam@gmail.com, alex@voxelbotics.com,
andrew@lunn.ch
Subject: Re: [PATCH v2 0/3] Add support for Emcraft Systems NavQ+ kit
Date: Wed, 3 Apr 2024 09:15:21 +0800 [thread overview]
Message-ID: <ZgytqXy/S63iXbTD@dragon> (raw)
In-Reply-To: <20240330133410.41408-1-gilles.talis@gmail.com>
On Sat, Mar 30, 2024 at 09:34:07AM -0400, Gilles Talis wrote:
> Hello
>
> This series adds a device tree file for the Emcraft Systems NavQ+ kit [1]
>
> The first patch adds a new vendor prefix for Emcraft Systems
> The second one adds the board to the arm/fsl.yaml DT bindings.
> Last patch adds device tree file for the kit.
>
> [1] https://www.emcraft.com/products/1222
>
> Changes in v2:
> - Add Acked-by review tags
> - Fixed device tree warnings reported by dtbs_check
> - Reworked leds node
> - Remove unused i2c6 pinctrl entry
> - Removed unused regulator node in Ethernet entry
> - Link to v1: https://lore.kernel.org/imx/20240328202320.187596-1-gilles.talis@gmail.com/
> ---
> Gilles Talis (3):
> dt-bindings: vendor-prefixes: Add Emcraft Systems
> dt-bindings: arm: Add Emcraft Systems i.MX8M Plus NavQ+ Kit
> arm64: dts: freescale: Add device tree for Emcraft Systems NavQ+ Kit
Applied all, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-04-03 1:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 13:34 [PATCH v2 0/3] Add support for Emcraft Systems NavQ+ kit Gilles Talis
2024-03-30 13:34 ` Gilles Talis
2024-03-30 13:34 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add Emcraft Systems Gilles Talis
2024-03-30 13:34 ` Gilles Talis
2024-03-30 13:34 ` [PATCH v2 2/3] dt-bindings: arm: Add Emcraft Systems i.MX8M Plus NavQ+ Kit Gilles Talis
2024-03-30 13:34 ` Gilles Talis
2024-03-30 13:34 ` [PATCH v2 3/3] arm64: dts: freescale: Add device tree for Emcraft Systems " Gilles Talis
2024-03-30 13:34 ` Gilles Talis
2024-03-30 16:46 ` Andrew Lunn
2024-03-30 16:46 ` Andrew Lunn
2024-03-30 17:03 ` Fabio Estevam
2024-03-30 17:03 ` Fabio Estevam
2024-04-03 1:15 ` Shawn Guo [this message]
2024-04-03 1:15 ` [PATCH v2 0/3] Add support for Emcraft Systems NavQ+ kit Shawn Guo
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=ZgytqXy/S63iXbTD@dragon \
--to=shawnguo2@yeah.net \
--cc=alex@voxelbotics.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gilles.talis@gmail.com \
--cc=imx@lists.linux.dev \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.org \
--cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.