From: Shawn Guo <shawnguo@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
David Jander <david@protonic.nl>,
Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/3] mainline add Altesco I6P board
Date: Tue, 10 Nov 2020 08:43:08 +0800 [thread overview]
Message-ID: <20201110004307.GG31601@dragon> (raw)
In-Reply-To: <20201030140029.22329-1-o.rempel@pengutronix.de>
On Fri, Oct 30, 2020 at 03:00:26PM +0100, Oleksij Rempel wrote:
> changes v2:
> - rebase against
> git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git for-next
> - remove spaces
> - use Co-developed-by instead of Co-Developed-by
>
> Oleksij Rempel (3):
> dt-bindings: vendor-prefixes: Add an entry for Altus-Escon-Company
> dt-bindings: arm: fsl: add Altesco I6P board
> ARM: dts: add Altesco I6P board
Applied all, 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: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
devicetree@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
David Jander <david@protonic.nl>
Subject: Re: [PATCH v2 0/3] mainline add Altesco I6P board
Date: Tue, 10 Nov 2020 08:43:08 +0800 [thread overview]
Message-ID: <20201110004307.GG31601@dragon> (raw)
In-Reply-To: <20201030140029.22329-1-o.rempel@pengutronix.de>
On Fri, Oct 30, 2020 at 03:00:26PM +0100, Oleksij Rempel wrote:
> changes v2:
> - rebase against
> git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git for-next
> - remove spaces
> - use Co-developed-by instead of Co-Developed-by
>
> Oleksij Rempel (3):
> dt-bindings: vendor-prefixes: Add an entry for Altus-Escon-Company
> dt-bindings: arm: fsl: add Altesco I6P board
> ARM: dts: add Altesco I6P board
Applied all, thanks.
next prev parent reply other threads:[~2020-11-10 0:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 14:00 [PATCH v2 0/3] mainline add Altesco I6P board Oleksij Rempel
2020-10-30 14:00 ` Oleksij Rempel
2020-10-30 14:00 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add an entry for Altus-Escon-Company Oleksij Rempel
2020-10-30 14:00 ` Oleksij Rempel
2020-10-30 14:00 ` [PATCH v2 2/3] dt-bindings: arm: fsl: add Altesco I6P board Oleksij Rempel
2020-10-30 14:00 ` Oleksij Rempel
2020-10-30 14:00 ` [PATCH v2 3/3] ARM: dts: " Oleksij Rempel
2020-10-30 14:00 ` Oleksij Rempel
2020-11-10 0:43 ` Shawn Guo [this message]
2020-11-10 0:43 ` [PATCH v2 0/3] mainline " 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=20201110004307.GG31601@dragon \
--to=shawnguo@kernel.org \
--cc=david@protonic.nl \
--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=mark.rutland@arm.com \
--cc=o.rempel@pengutronix.de \
--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.