From: Tom Rini <trini@konsulko.com>
To: Leo Liang <ycliang@andestech.com>
Cc: u-boot@lists.denx.de, rick@andestech.com
Subject: Re: [PULL] u-boot-riscv/riscv-for-next
Date: Thu, 6 Jul 2023 16:02:22 -0400 [thread overview]
Message-ID: <20230706200222.GE7930@bill-the-cat> (raw)
In-Reply-To: <ZKabX3HI7USoCEEt@ubuntu01>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
On Thu, Jul 06, 2023 at 10:45:51AM +0000, Leo Liang wrote:
> Hi Tom,
>
> The following changes since commit e80f4079b3a3db0961b73fa7a96e6c90242d8d25:
>
> Merge tag 'v2023.07-rc6' into next (2023-07-05 11:28:55 -0400)
>
> are available in the Git repository at:
>
> https://source.denx.de/u-boot/custodians/u-boot-riscv.git riscv-for-next
>
> for you to fetch changes up to 12f66e2197c59e500d1e2ee359bb2ce22d748290:
>
> board: ae350: Add missing env variables for booti (2023-07-06 17:28:08 +0800)
>
> CI result shows no issue: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/16799
>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2023-07-06 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 10:45 [PULL] u-boot-riscv/riscv-for-next Leo Liang
2023-07-06 20:02 ` 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=20230706200222.GE7930@bill-the-cat \
--to=trini@konsulko.com \
--cc=rick@andestech.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.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 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 NNTP newsgroup(s).