From: Leo Liang <ycliang@andestech.com>
To: Tom Rini <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>, <rick@andestech.com>, <bmeng.cn@gmail.com>
Subject: Re: [PULL v2] u-boot-riscv/next
Date: Thu, 17 Jun 2021 09:49:04 +0800 [thread overview]
Message-ID: <20210617014903.GA16800@andestech.com> (raw)
In-Reply-To: <20210616145918.GU9516@bill-the-cat>
On Wed, Jun 16, 2021 at 10:59:18AM -0400, Tom Rini wrote:
> On Wed, Jun 16, 2021 at 08:48:40PM +0800, Leo Liang 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 d1d256e1635684615182aaf62b077233c3360f7e:
> >
> > riscv: andes_plic: Fix riscv_get_ipi() mask (2021-06-16 16:20:13 +0800)
> >
> > CI result shows no issue: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/7857
> >
>
> This is not based on u-boot/next, but rather on u-boot/master. Is there
> something currently in master that you need for this PR? If so, I can
> merge in a later -rc tag. Otherwise please rebase this on next itself,
> thanks.
>
> --
> Tom
Hi Tom,
Sorry for the confusion.
I think I will follow Bin's suggestion,
split it into two PRs,
the fixes for -rc, and k210 clk for next,
and re-send it later.
Thanks for your help and heads up!
Best regards,
Leo
prev parent reply other threads:[~2021-06-17 1:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 12:48 [PULL v2] u-boot-riscv/next Leo Liang
2021-06-16 14:59 ` Tom Rini
2021-06-16 22:58 ` Bin Meng
2021-06-17 1:51 ` Leo Liang
2021-06-17 1:49 ` Leo Liang [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=20210617014903.GA16800@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