From: sbabic@denx.de
To: Adam Ford <aford173@gmail.com>,u-boot@lists.denx.de
Subject: [PATCH 1/5] imx: imx8mm-beacon: Move environment definition to env file
Date: Tue, 11 Jul 2023 21:46:54 +0200 (CEST) [thread overview]
Message-ID: <20230711194656.492108693D@phobos.denx.de> (raw)
In-Reply-To: <20230528191805.66713-1-aford173@gmail.com>
> Instead of cluttering up a header file with a bunch of defines,
> move the default environmental variables to a file called
> imx8mm_beacon.env and reference it from the defconfig.
> Signed-off-by: Adam Ford <aford173@gmail.com>
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, 82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================
prev parent reply other threads:[~2023-07-11 19:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 19:18 [PATCH 1/5] imx: imx8mm-beacon: Move environment definition to env file Adam Ford
2023-05-28 19:18 ` [PATCH 2/5] imx8m: imx8mm-beacon: Migrate README to rst Adam Ford
2023-07-11 19:45 ` sbabic
2023-05-28 19:18 ` [PATCH 3/5] imx: imx8mn-beacon: Move environment definition to env file Adam Ford
2023-07-11 19:45 ` sbabic
2023-05-28 19:18 ` [PATCH 4/5] imx8m: imx8mn-beacon: Migrate README to rst Adam Ford
2023-07-11 19:42 ` sbabic
2023-05-28 19:18 ` [PATCH 5/5] imx8m: beacon: Update MAINTAINER file to include beacon rst files Adam Ford
2023-07-11 19:44 ` sbabic
2023-06-12 12:53 ` [PATCH 1/5] imx: imx8mm-beacon: Move environment definition to env file Adam Ford
2023-06-12 16:27 ` Tom Rini
2023-07-17 15:58 ` Adam Ford
2023-07-11 19:46 ` sbabic [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=20230711194656.492108693D@phobos.denx.de \
--to=sbabic@denx.de \
--cc=aford173@gmail.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox