From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] configs/imx6ullevk: new defconfig board/freescale/imx6ullevk/readme.txt: new readme for the imx6ullevk board. DEVELOPERS: Add myself as the maintainer of imx6ullevk.
Date: Mon, 13 Apr 2020 15:53:06 +0200 [thread overview]
Message-ID: <20200413155306.78792b5f@windsurf.home> (raw)
In-Reply-To: <20190926181419.18710-1-jeffrey.kinross@i3pd.com>
Hello Jeffrey,
On Thu, 26 Sep 2019 13:14:20 -0500
Jeffrey Kinross <jeffrey.kinross@i3pd.com> wrote:
> Changes v1 -> v2:
> - DEVELOPERS - Add myself as maintainer of configs/imx6ullevk (suggested by Gilles Talis)
> - configs/imx6ullevk - Use the FSL kernel and uboot. Pin the kernel and uboot version (suggested by Thomas Petazzoni)
>
> configs/imx6ullevk: new defconfig
> board/freescale/imx6ullevk/readme.txt: new readme for the imx6ullevk board.
> DEVELOPERS: Add myself as the maintainer of imx6ullevk.
>
> Add support for imx6ullevk board, using the kernel and uboot from the FSL Community BSP.
>
> Signed-off-by: Jeffrey Kinross <jeffrey.kinross@i3pd.com>
Thanks a lot for your contribution. However in the mean time, we have
merged
https://git.buildroot.org/buildroot/tree/configs/freescale_imx6ullevk_defconfig
which supports the same board, also with the NXP-provided kernel and
U-Boot.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-04-13 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 20:45 [Buildroot] [PATCH 1/1] configs/imx6ullevk: add imx6ullevk support jeffrey.kinross at i3pd.com
2019-07-06 8:47 ` Gilles Talis
2019-09-25 21:17 ` Thomas Petazzoni
2019-09-26 18:14 ` [Buildroot] [PATCH v2] configs/imx6ullevk: new defconfig board/freescale/imx6ullevk/readme.txt: new readme for the imx6ullevk board. DEVELOPERS: Add myself as the maintainer of imx6ullevk Jeffrey Kinross
2020-04-13 13:53 ` Thomas Petazzoni [this message]
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=20200413155306.78792b5f@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox