From: Tom Rini <trini@konsulko.com>
To: Bryan Brattlof <bb@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>, Andrew Davis <afd@ti.com>,
Judith Mendez <jm@ti.com>, Kamlesh Gurudasani <kamlesh@ti.com>,
UBoot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 4/5] configs: am62a: convert bootcmd to distro_bootcmd
Date: Tue, 10 Jan 2023 21:17:10 -0500 [thread overview]
Message-ID: <20230111021710.GD3787616@bill-the-cat> (raw)
In-Reply-To: <20221224011525.4696-5-bb@ti.com>
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
On Fri, Dec 23, 2022 at 07:15:24PM -0600, Bryan Brattlof wrote:
> We're currently using CONFIG_BOOTCOMMAND to run custom boot scripts to
> jump into linux. While this works, let's begin the transition to more
> distribution friendly jumps to linux by enabling distro_bootcmd.
>
> Convert the custom bootcmd to a distro_bootcmd
>
> Signed-off-by: Judith Mendez <jm@ti.com>
> Signed-off-by: Bryan Brattlof <bb@ti.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-01-11 2:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 1:15 [PATCH 0/5] add support for hs bootflows to am62a Bryan Brattlof
2022-12-24 1:15 ` [PATCH 1/5] configs: restrict am62ax wakup SPL size Bryan Brattlof
2023-01-11 2:16 ` Tom Rini
2022-12-24 1:15 ` [PATCH 2/5] configs: am62a: move stack and heap to HSM RAM Bryan Brattlof
2023-01-11 2:17 ` Tom Rini
2022-12-24 1:15 ` [PATCH 3/5] arm: mach-k3: copy bootindex to OCRAM for main domain SPL Bryan Brattlof
2023-01-11 2:17 ` Tom Rini
2022-12-24 1:15 ` [PATCH 4/5] configs: am62a: convert bootcmd to distro_bootcmd Bryan Brattlof
2023-01-11 2:17 ` Tom Rini [this message]
2022-12-24 1:15 ` [PATCH 5/5] configs: am62a: use kernel fitImage when using secure bootflow Bryan Brattlof
2023-01-11 2:17 ` Tom Rini
2022-12-29 9:14 ` [PATCH 0/5] add support for hs bootflows to am62a Kamlesh Gurudasani
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=20230111021710.GD3787616@bill-the-cat \
--to=trini@konsulko.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=jm@ti.com \
--cc=kamlesh@ti.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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.