From: Shawn Guo <shawnguo@kernel.org>
To: Adam Ford <aford173@gmail.com>
Cc: devicetree@vger.kernel.org, Sascha Hauer <s.hauer@pengutronix.de>,
aford@beaconembedded.com, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: dts: imx: Add Beacon i.MX8m-Mini development kit
Date: Thu, 23 Apr 2020 22:21:36 +0800 [thread overview]
Message-ID: <20200423142135.GB9391@dragon> (raw)
In-Reply-To: <20200324144324.21178-2-aford173@gmail.com>
On Tue, Mar 24, 2020 at 09:43:23AM -0500, Adam Ford wrote:
> Beacon Embeddedworks is launching a development kit based on the
> i.MX8M Mini SoC. The kit consists of a System on Module (SOM)
> + baseboard. The SOM has the SoC, eMMC, and Ethernet. The baseboard
> has an wm8962 audio CODEC, a single USB OTG, and three USB host ports.
>
> Signed-off-by: Adam Ford <aford173@gmail.com>
Applied, thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Adam Ford <aford173@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, aford@beaconembedded.com,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: imx: Add Beacon i.MX8m-Mini development kit
Date: Thu, 23 Apr 2020 22:21:36 +0800 [thread overview]
Message-ID: <20200423142135.GB9391@dragon> (raw)
In-Reply-To: <20200324144324.21178-2-aford173@gmail.com>
On Tue, Mar 24, 2020 at 09:43:23AM -0500, Adam Ford wrote:
> Beacon Embeddedworks is launching a development kit based on the
> i.MX8M Mini SoC. The kit consists of a System on Module (SOM)
> + baseboard. The SOM has the SoC, eMMC, and Ethernet. The baseboard
> has an wm8962 audio CODEC, a single USB OTG, and three USB host ports.
>
> Signed-off-by: Adam Ford <aford173@gmail.com>
Applied, thanks.
next prev parent reply other threads:[~2020-04-23 14:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 14:43 [PATCH 1/2] dt-bindings: vendor-prefixes: Add Beacon vendor prefix Adam Ford
2020-03-24 14:43 ` Adam Ford
2020-03-24 14:43 ` [PATCH 2/2] arm64: dts: imx: Add Beacon i.MX8m-Mini development kit Adam Ford
2020-03-24 14:43 ` Adam Ford
2020-03-26 13:19 ` Fabio Estevam
2020-03-26 13:19 ` Fabio Estevam
2020-04-11 1:35 ` Adam Ford
2020-04-11 1:35 ` Adam Ford
2020-04-23 14:21 ` Shawn Guo [this message]
2020-04-23 14:21 ` Shawn Guo
2020-03-31 20:02 ` [PATCH 1/2] dt-bindings: vendor-prefixes: Add Beacon vendor prefix Rob Herring
2020-03-31 20:02 ` Rob Herring
2020-04-23 3:10 ` Shawn Guo
2020-04-23 3:10 ` Shawn Guo
2020-04-23 3:49 ` Fabio Estevam
2020-04-23 3:49 ` Fabio Estevam
2020-04-23 14:21 ` Shawn Guo
2020-04-23 14:21 ` 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=20200423142135.GB9391@dragon \
--to=shawnguo@kernel.org \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.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=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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.