From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Charles Hardin <ckhardin@gmail.com>
Cc: Gary Bisson <bisson.gary@gmail.com>,
Refik Tuzakli <tuzakli.refik@gmail.com>,
Maeva Manuel <maeva.manuel@oss.nxp.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] packages/imx-seco: add the imx8dxl b0 revsision ahab image
Date: Mon, 10 Jul 2023 21:32:23 +0200 [thread overview]
Message-ID: <20230710213223.5b49c915@windsurf> (raw)
In-Reply-To: <20230620171943.3999-1-ckhardin@gmail.com>
Hello Charles,
On Tue, 20 Jun 2023 10:19:43 -0700
Charles Hardin <ckhardin@gmail.com> wrote:
> Update the selection of the ahab container images for the imx8dxl
> asics. The initial support assumed these were imx8 but this is
> actually the imx8x architecture as well. This was fixed when run on
> the first tests against the imx8dxl SoCs.
>
> Files from upstream:
> mx8dxla0-ahab-container.img
> mx8dxla1-ahab-container.img
> mx8dxlb0-ahab-container.img
>
> The B0 revision should be considered the latest
>
> Signed-off-by: Charles Hardin <ckhardin@gmail.com>
> ---
> package/freescale-imx/imx-seco/Config.in | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
I've applied, but I would have preferred two patches: one fixing the
existing entries, one adding the new entry, as these are completely
different things.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-10 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 17:19 [Buildroot] [PATCH 1/1] packages/imx-seco: add the imx8dxl b0 revsision ahab image Charles Hardin
2023-07-10 19:32 ` Thomas Petazzoni via buildroot [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=20230710213223.5b49c915@windsurf \
--to=buildroot@buildroot.org \
--cc=bisson.gary@gmail.com \
--cc=ckhardin@gmail.com \
--cc=maeva.manuel@oss.nxp.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tuzakli.refik@gmail.com \
/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.