From: Fabio Estevam <festevam@gmail.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Sascha Hauer <kernel@pengutronix.de>,
"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>
Subject: Re: [PATCH v2] ARM: DTS: imx53: Add support for imx53 HSC/DDC boards from K+P
Date: Tue, 29 May 2018 12:12:43 -0300 [thread overview]
Message-ID: <CAOMZO5BiKjoiyh0dxycRhPkRzS2Uk9h8fPTA+sXMZBDJpbcyWQ@mail.gmail.com> (raw)
In-Reply-To: <20180519121506.32344-1-lukma@denx.de>
On Sat, May 19, 2018 at 9:15 AM, Lukasz Majewski <lukma@denx.de> wrote:
> This commit provides support for HSC and DDC boards from
> Kieback&Peter GmbH vendor.
>
> Signed-off-by: Lukasz Majewski <lukma@denx.de>
Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
WARNING: multiple messages have this Message-ID (diff)
From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: DTS: imx53: Add support for imx53 HSC/DDC boards from K+P
Date: Tue, 29 May 2018 12:12:43 -0300 [thread overview]
Message-ID: <CAOMZO5BiKjoiyh0dxycRhPkRzS2Uk9h8fPTA+sXMZBDJpbcyWQ@mail.gmail.com> (raw)
In-Reply-To: <20180519121506.32344-1-lukma@denx.de>
On Sat, May 19, 2018 at 9:15 AM, Lukasz Majewski <lukma@denx.de> wrote:
> This commit provides support for HSC and DDC boards from
> Kieback&Peter GmbH vendor.
>
> Signed-off-by: Lukasz Majewski <lukma@denx.de>
Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
next prev parent reply other threads:[~2018-05-29 15:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 15:34 [PATCH] ARM: DTS: imx53: Add support for imx53 HSC/DDC boards from K+P Lukasz Majewski
2018-05-09 15:34 ` Lukasz Majewski
2018-05-10 1:10 ` Fabio Estevam
2018-05-10 1:10 ` Fabio Estevam
2018-05-19 12:02 ` Lukasz Majewski
2018-05-19 12:02 ` Lukasz Majewski
2018-05-23 13:56 ` Fabio Estevam
2018-05-23 13:56 ` Fabio Estevam
2018-05-23 22:18 ` Lukasz Majewski
2018-05-23 22:18 ` Lukasz Majewski
2018-05-29 13:58 ` Lukasz Majewski
2018-05-29 13:58 ` Lukasz Majewski
2018-05-29 14:11 ` Fabio Estevam
2018-05-29 14:11 ` Fabio Estevam
2018-05-29 15:09 ` Lukasz Majewski
2018-05-29 15:09 ` Lukasz Majewski
2018-05-10 1:45 ` Fabio Estevam
2018-05-10 1:45 ` Fabio Estevam
2018-05-19 12:15 ` [PATCH v2] " Lukasz Majewski
2018-05-19 12:15 ` Lukasz Majewski
2018-05-29 15:12 ` Fabio Estevam [this message]
2018-05-29 15:12 ` Fabio Estevam
2018-06-07 8:51 ` Lukasz Majewski
2018-06-07 8:51 ` Lukasz Majewski
2018-06-11 5:13 ` Shawn Guo
2018-06-11 5:13 ` Shawn Guo
2018-06-12 11:28 ` Lukasz Majewski
2018-06-12 11:28 ` Lukasz Majewski
2018-06-12 13:32 ` [PATCH v3] " Lukasz Majewski
2018-06-12 13:32 ` Lukasz Majewski
2018-06-17 6:57 ` Shawn Guo
2018-06-17 6:57 ` Shawn Guo
2018-06-17 7:31 ` Lukasz Majewski
2018-06-17 7:31 ` Lukasz Majewski
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=CAOMZO5BiKjoiyh0dxycRhPkRzS2Uk9h8fPTA+sXMZBDJpbcyWQ@mail.gmail.com \
--to=festevam@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukma@denx.de \
--cc=mark.rutland@arm.com \
--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.