From: Tom Rini <trini@konsulko.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
Samuel Holland <samuel@sholland.org>,
Maksim Kiselev <bigunclemax@gmail.com>,
Nick Alilovic <nickalilovic@gmail.com>,
Chuanhong Guo <gch981213@gmail.com>,
linux-sunxi@lists.linux.dev, u-boot@lists.denx.de
Subject: Re: Pull request: u-boot-sunxi/master for v2024.04
Date: Mon, 29 Jan 2024 12:34:18 -0500 [thread overview]
Message-ID: <20240129173418.GA1152441@bill-the-cat> (raw)
In-Reply-To: <20240129172449.0b9ebc9f@donnerap.manchester.arm.com>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
On Mon, Jan 29, 2024 at 05:24:49PM +0000, Andre Przywara wrote:
> On Mon, 29 Jan 2024 15:55:43 +0000
> Andre Przywara <andre.przywara@arm.com> wrote:
>
> Hi Tom,
>
> > please pull the sunxi/master branch, containing the first part of the
>
> I just saw that the CI pipeline failed on missing maintainer entries for
> the two new boards. Is that a showstopper for you? Shall I update the
> branch, or would a follow-up patch be sufficient?
I've fixed this up myself this time, since I was doing another CI run
with this for other changes but in the future please fix these errors
before sending the PR.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-01-29 17:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 15:55 Pull request: u-boot-sunxi/master for v2024.04 Andre Przywara
2024-01-29 17:24 ` Andre Przywara
2024-01-29 17:34 ` Tom Rini [this message]
2024-01-29 17:50 ` Andre Przywara
2024-01-29 17:55 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2024-03-05 11:15 Andre Przywara
2024-03-05 13:27 ` 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=20240129173418.GA1152441@bill-the-cat \
--to=trini@konsulko.com \
--cc=andre.przywara@arm.com \
--cc=bigunclemax@gmail.com \
--cc=gch981213@gmail.com \
--cc=jagan@amarulasolutions.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=nickalilovic@gmail.com \
--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