From: Gary Bisson <gary.bisson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/freescale-imx/imx-seco: bump version to 3.6.3
Date: Thu, 9 Jul 2020 17:12:03 +0200 [thread overview]
Message-ID: <20200709151203.GA762644@p1g2> (raw)
In-Reply-To: <20200709144457.5682-1-maeva.manuel@oss.nxp.com>
Hi Maeva,
On Thu, Jul 09, 2020 at 04:44:57PM +0200, Maeva Manuel wrote:
> This version is aligned with 5.4.24_2.1.0 NXP Linux BSP.
> Firmware file names now include the SoC revision.
>
> In order not to break the compatibility with the imx-seco 2.3.1 package,
> it remains B0 support for i.MX8QXP MEK.
> C0 support should introduce a Kconfig and this will be done in a future
> patch.
>
> License was updated from:
> LA_OPT_NXP_Software_License v10 December 2019
> to:
> LA_OPT_NXP_Software_License v11 February 2020
> which explains the change of EULA/COPYING license files.
>
> Tested-by: Maeva Manuel <maeva.manuel@oss.nxp.com>
> [Maeva: tested on i.MX8QXP MEK (Board rev D1, SoC rev B0)
> and on i.MX8QM MEK (SoC rev B0)]
> Signed-off-by: Maeva Manuel <maeva.manuel@oss.nxp.com>
Reviewed-by: Gary Bisson <gary.bisson@boundarydevices.com>
Thanks for spinning the v2 quickly and for the contribution.
Regards,
Gary
next prev parent reply other threads:[~2020-07-09 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 7:43 [Buildroot] [PATCH 1/1] package/freescale-imx/imx-seco: bump version to 3.6.3 Maeva Manuel
2020-07-08 12:14 ` Gary Bisson
2020-07-09 6:54 ` Maeva Manuel
2020-07-09 7:30 ` Heiko Thiery
2020-07-09 7:44 ` Gary Bisson
2020-07-09 14:44 ` [Buildroot] [PATCH v2 " Maeva Manuel
2020-07-09 15:12 ` Gary Bisson [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-10 8:16 [Buildroot] [PATCH 1/1] package/freescale-imx/firmware-imx: bump version to 8.8 Maeva Manuel
2020-07-10 8:16 ` [Buildroot] [PATCH v2 1/1] package/freescale-imx/imx-seco: bump version to 3.6.3 Maeva Manuel
2020-07-12 8:55 ` Thomas Petazzoni
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=20200709151203.GA762644@p1g2 \
--to=gary.bisson@boundarydevices.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