From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] test/py: Make the number of SPL banners seen a variable
Date: Wed, 08 May 2024 17:17:37 -0600 [thread overview]
Message-ID: <171521025710.3157089.5386675417640932585.b4-ty@konsulko.com> (raw)
In-Reply-To: <20240424224537.1614937-1-trini@konsulko.com>
On Wed, 24 Apr 2024 16:45:37 -0600, Tom Rini wrote:
> Currently we have the option to tell the console code that we should
> ignore the SPL banner. We also have an option to say that we can see it
> a second time, and ignore it. However, some platforms such as TI AM64x
> will have us see the SPL banner three times. Rather than add an
> "spl3_skipped" option, rework the code. By default we expect to see the
> banner once, but boards can specify seeing it as many times as they
> expect to.
>
> [...]
Applied to u-boot/next, thanks!
--
Tom
prev parent reply other threads:[~2024-05-08 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 22:45 [PATCH] test/py: Make the number of SPL banners seen a variable Tom Rini
2024-05-08 23:17 ` Tom Rini [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=171521025710.3157089.5386675417640932585.b4-ty@konsulko.com \
--to=trini@konsulko.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).