From: Leo Liang <ycliang@andestech.com>
To: Bin Meng <bmeng.cn@gmail.com>, <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>, <rick@andestech.com>
Subject: Re: [PULL] u-boot-riscv/next
Date: Wed, 16 Jun 2021 16:28:21 +0800 [thread overview]
Message-ID: <20210616082821.GA19880@andestech.com> (raw)
In-Reply-To: <CAEUhbmV-eZftTd7YiCRFK02SRK0nM7wUd6ff34PdUzWifLYqDw@mail.gmail.com>
On Wed, Jun 16, 2021 at 04:07:26PM +0800, Bin Meng wrote:
> Hi Leo,
>
> On Wed, Jun 16, 2021 at 3:44 PM Leo Liang <ycliang@andestech.com> wrote:
> >
> > Hi Tom,
> >
> > Please pull u-boot-riscv/next into -next.
> >
> > The following changes on the "next" branch since commit c4737cd594b5c4c47aff789fc53f7dd36ed03c94:
> >
> > Merge tag 'xilinx-for-v2021.07-rc5' of https://source.denx.de/u-boot/custodians/u-boot-microblaze (2021-06-11 08:29:34 -0400)
> >
> > are available in the Git repository at:
> >
> > git@source.denx.de:u-boot/custodians/u-boot-riscv.git
> >
> > for you to fetch changes up to efbcd66af3c83b14efb72eb38f73cd4af8128208:
> >
> > test: Add K210 PLL tests to sandbox defconfigs (2021-06-16 10:04:23 +0800)
> >
> > CI result shows no issue: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/7856
> >
> > ----------------------------------------------------------------
> > Bin Meng (6):
> > riscv: ae350: dts: Add SPDX license header
> > riscv: ae350: dts: Remove the unnecessary space in bootargs
> > riscv: ae350: dts: Remove the unnecessary #address-cells in plic nodes
> > riscv: ae350: dts: Fix #interrupt-cells for plic0 in 32-bit
> > riscv: ae350: dts: Add missing "u-boot, dm-spl" for SPL config
> > riscv: ae350: doc: Remove CONFIG_SKIP_LOWLEVEL_INIT
>
> It seems this patch is missing?
>
> riscv: andes_plic: Fix riscv_get_ipi() mask
> http://patchwork.ozlabs.org/project/uboot/patch/20210615054557.376750-1-bmeng.cn@gmail.com/
>
> Regards,
> Bin
Hi Bin,
Sorry, I must have omitted it by accident.
Hi Tom,
Could you drop this PR ?
I will send another one including the patch Bin mentioned.
Thanks!
Best regards,
Leo
next prev parent reply other threads:[~2021-06-16 8:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 7:44 [PULL] u-boot-riscv/next Leo Liang
2021-06-16 8:07 ` Bin Meng
2021-06-16 8:28 ` Leo Liang [this message]
2021-06-16 12:06 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2022-09-26 7:39 Leo Liang
2022-09-27 12:53 ` Tom Rini
2023-09-21 1:28 Leo Liang
2023-09-21 19:56 ` Tom Rini
2024-09-12 6:39 Leo Liang
2024-09-12 17:44 ` Tom Rini
2025-06-03 6:45 Leo Liang
2025-06-05 20:05 ` Tom Rini
2025-06-08 2:37 ` Yao Zi
2025-06-09 8:04 ` Leo Liang
2025-06-30 12:02 ` Leo Liang
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=20210616082821.GA19880@andestech.com \
--to=ycliang@andestech.com \
--cc=bmeng.cn@gmail.com \
--cc=rick@andestech.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