From: Tom Rini <trini@konsulko.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
u-boot@lists.denx.de, linux-sunxi@lists.linux.dev,
Samuel Holland <samuel@sholland.org>,
Mark Kettenis <kettenis@openbsd.org>
Subject: Re: Pull request: u-boot-sunxi/master for 2023.01
Date: Sun, 18 Dec 2022 20:59:30 -0500 [thread overview]
Message-ID: <20221219015930.GJ3787616@bill-the-cat> (raw)
In-Reply-To: <20221217015114.1264-1-andre.przywara@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On Sat, Dec 17, 2022 at 01:51:14AM +0000, Andre Przywara wrote:
> Hi Tom,
>
> please pull some fixes for sunxi.
> This cleans up each board's defconfig, and fixes the serial console on
> some Olimex board. Also we lose another legacy config variable.
> The rest are minor cleanups, that actually shouldn't change anything
> in the build.
>
> Passed the gitlab CI, plus briefly tested on Pine64-LTS, LicheePi Nano,
> and BananaPi M1.
>
> Thanks,
> Andre
> ========================
> The following changes since commit c917865c7fd14420d25388bb3c8c24cb03911caf:
>
> Merge https://source.denx.de/u-boot/custodians/u-boot-marvell (2022-12-12 09:00:58 -0500)
>
> are available in the Git repository at:
>
> https://source.denx.de/u-boot/custodians/u-boot-sunxi.git master
>
> for you to fetch changes up to 64531496f990c2a63211c72b953dfc084b4c2589:
>
> sunxi: board: annotate #endif lines (2022-12-14 22:31:33 +0000)
>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-12-19 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 1:51 Pull request: u-boot-sunxi/master for 2023.01 Andre Przywara
2022-12-19 1:59 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-19 23:54 Andre Przywara
2022-10-20 19:02 ` Tom Rini
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=20221219015930.GJ3787616@bill-the-cat \
--to=trini@konsulko.com \
--cc=andre.przywara@arm.com \
--cc=jagan@amarulasolutions.com \
--cc=kettenis@openbsd.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--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