From: Andrea Calabrese <andrea.calabrese@amarulasolutions.com>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, michael@amarulasolutions.com,
dario.binacchi@amarulasolutions.com, festevam@gmail.com
Subject: Re: [PATCH v2 1/3] bsh: update readme with instructions to build M2B
Date: Fri, 31 Oct 2025 08:45:22 +0100 [thread overview]
Message-ID: <22fb0887-e1a2-4a0e-8b8a-5b49e78ebfbf@amarulasolutions.com> (raw)
In-Reply-To: <20251030133649.GR6688@bill-the-cat>
You are right, I used a tool to verify everything was in order, but I
did it in the last commit... Will send a v3.
Il 30/10/25 14:36, Tom Rini ha scritto:
> On Thu, Oct 30, 2025 at 09:47:08AM +0100, Andrea Calabrese wrote:
>
>> readme was missing instructions to build M2B. Now added.
>>
>> Signed-off-by: Andrea Calabrese <andrea.calabrese@amarulasolutions.com>
> [snip]
>> diff --git a/doc/board/bsh/imx6ulz_bsh_smm_m2.rst b/doc/board/bsh/imx6ulz_bsh_smm_m2.rst
>> new file mode 100644
>> index 00000000000..c61dbfe2ae7
>> --- /dev/null
>> +++ b/doc/board/bsh/imx6ulz_bsh_smm_m2.rst
>> @@ -0,0 +1,85 @@
>> +.. SPDX-License-Identifier: GPL-2.0+
>> +
>> +How to Update U-Boot on imx6ulz_smm_m2 and imx6ulz_smm_m2b boards
>> +==================================================================================
> Please see doc/build/documentation.rst for how to build the
> documentation as there's errors here that will trip CI. Headings (===)
> need to be the exact length as the text. Everything else is probably
> fine but I can't always spot spacing errors without building. I don't
> know if Fabio wants to fix this part up when applying. Thanks!
>
--
Andrea Calabrese
Embedded Software Developer
M. +39 339 394 4747
andrea.calabrese@amarulasolutions.com
__________________________________
Amarula Solutions BV
Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9170
info@amarulasolutions.com
www.amarulasolutions.com
__________________________________
This message and any file transmitted with it may contain privileged or confidential information. In case you were not listed in the addressed recipient, please notify the sender immediately and delete the message.
Any other use of this email, including copying it and the disclosure of its content, is prohibited.
prev parent reply other threads:[~2025-10-31 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 8:47 [PATCH v2 1/3] bsh: update readme with instructions to build M2B Andrea Calabrese
2025-10-30 8:47 ` [PATCH v2 2/3] bsh: imx6ulz_smm_m2: Update imx6ulz BSH SMM M2B board Andrea Calabrese
2025-10-30 8:47 ` [PATCH v2 3/3] bsh: imx6ulz_smm_m2: Add imx6ulz BSH SMM M2D board Andrea Calabrese
2025-10-30 13:36 ` [PATCH v2 1/3] bsh: update readme with instructions to build M2B Tom Rini
2025-10-31 7:45 ` Andrea Calabrese [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=22fb0887-e1a2-4a0e-8b8a-5b49e78ebfbf@amarulasolutions.com \
--to=andrea.calabrese@amarulasolutions.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=festevam@gmail.com \
--cc=michael@amarulasolutions.com \
--cc=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