All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
	kernel@dh-electronics.com
Subject: Re: [PATCH] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02 boards
Date: Mon, 24 May 2021 10:02:50 -0300	[thread overview]
Message-ID: <CAOMZO5D7P8Ae0zuyDbQhFAz6F4iRcoVW0euz2oCcK+CRHH5OMA@mail.gmail.com> (raw)
In-Reply-To: <20210524120917.6573-1-cniedermaier@dh-electronics.com>

Hi Christoph,

On Mon, May 24, 2021 at 9:17 AM Christoph Niedermaier
<cniedermaier@dh-electronics.com> wrote:

> +      - description: i.MX6S DHCOM DRC02 Board
> +        items:
> +          - const: dh,imx6s-dhcom-drc02
> +          - const: dh,imx6s-dhcom-som
> +          - const: fsl,imx6s

We don't have an fsl,imx6s compatible for the i.MX6 Solo variant. We
just use fsl,imx6dl instead.

WARNING: multiple messages have this Message-ID (diff)
From: Fabio Estevam <festevam@gmail.com>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	 "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	 Shawn Guo <shawnguo@kernel.org>,
	kernel@dh-electronics.com
Subject: Re: [PATCH] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02 boards
Date: Mon, 24 May 2021 10:02:50 -0300	[thread overview]
Message-ID: <CAOMZO5D7P8Ae0zuyDbQhFAz6F4iRcoVW0euz2oCcK+CRHH5OMA@mail.gmail.com> (raw)
In-Reply-To: <20210524120917.6573-1-cniedermaier@dh-electronics.com>

Hi Christoph,

On Mon, May 24, 2021 at 9:17 AM Christoph Niedermaier
<cniedermaier@dh-electronics.com> wrote:

> +      - description: i.MX6S DHCOM DRC02 Board
> +        items:
> +          - const: dh,imx6s-dhcom-drc02
> +          - const: dh,imx6s-dhcom-som
> +          - const: fsl,imx6s

We don't have an fsl,imx6s compatible for the i.MX6 Solo variant. We
just use fsl,imx6dl instead.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-05-24 13:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 12:09 [PATCH] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02 boards Christoph Niedermaier
2021-05-24 12:09 ` Christoph Niedermaier
2021-05-24 13:02 ` Fabio Estevam [this message]
2021-05-24 13:02   ` Fabio Estevam
  -- strict thread matches above, loose matches on Subject: below --
2021-05-24 12:03 Christoph Niedermaier
2021-05-24 12:03 ` Christoph Niedermaier

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=CAOMZO5D7P8Ae0zuyDbQhFAz6F4iRcoVW0euz2oCcK+CRHH5OMA@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=cniedermaier@dh-electronics.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@dh-electronics.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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.