From: Leo Liang <ycliang@andestech.com>
To: u-boot@lists.denx.de
Subject: [PULL] u-boot-riscv/master
Date: Fri, 7 May 2021 09:41:36 +0800 [thread overview]
Message-ID: <20210507014136.GA16808@andestech.com> (raw)
In-Reply-To: <20210507010943.GO17669@bill-the-cat>
On Fri, May 07, 2021 at 09:09:43AM +0800, Tom Rini wrote:
> On Fri, May 07, 2021 at 09:06:33AM +0800, Leo Liang wrote:
>
> > Hi Tom,
> >
> > CI result: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/7400
> >
> > The following changes since commit 8ddaf943589756442bba21e5be645cd47526d82b:
> >
> > Merge tag 'dm-pull-29apr21' of https://source.denx.de/u-boot/custodians/u-boot-dm (2021-04-29 21:03:38 -0400)
> >
> > are available in the Git repository at:
> >
> > https://source.denx.de/u-boot/custodians/u-boot-riscv.git
> >
> > for you to fetch changes up to 91e4b7516d84cefab7324765b3c8d6a909185ce2:
> >
> > cmd/exception: support ebreak exception on RISC-V (2021-05-05 16:13:12 +0800)
> >
> > ----------------------------------------------------------------
> > Dylan Jhong (1):
> > atcspi200: Add timeout mechanism in spi_xfer()
> >
> > Green Wan (2):
> > riscv: cpu: Add callback to init each core
> > riscv: cpu: fu740: clear feature disable CSR
> >
> > Heinrich Schuchardt (1):
> > cmd/exception: support ebreak exception on RISC-V
> >
> > arch/riscv/cpu/cpu.c | 11 +++++++++++
> > arch/riscv/cpu/fu540/spl.c | 15 +++++++++++++++
> > arch/riscv/cpu/start.S | 4 ++++
> > cmd/riscv/exception.c | 10 ++++++++++
> > doc/usage/exception.rst | 3 +++
> > drivers/spi/atcspi200_spi.c | 10 ++++++++--
> > 6 files changed, 51 insertions(+), 2 deletions(-)
>
> Please note that currently
> https://patchwork.ozlabs.org/project/uboot/list/?series=&submitter=&state=&q=&archive=&delegate=20174
> shows 55 patches. Most of them have been posted long enough that I
> would expect them to be applied if there's no further feedback. Can you
> please take a look? Thanks!
>
No problem, sorry for the delay!
Two quick questions.
Some of the patches delegated to Andes do not own a RISC-V tag but rather clk or driver etc.
Do you mind if we pull them through RISC-V tree?
And for these patches,
do you prefer them pulled into this release or for-next branch?
Best regards,
Leo
next prev parent reply other threads:[~2021-05-07 1:41 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 1:06 [PULL] u-boot-riscv/master Leo Liang
2021-05-07 1:09 ` Tom Rini
2021-05-07 1:41 ` Leo Liang [this message]
2021-05-07 1:55 ` Sean Anderson
2021-05-07 16:15 ` Tom Rini
2021-05-07 14:21 ` Dimitri John Ledkov
2021-05-07 14:35 ` Tom Rini
2021-05-07 1:49 ` Sean Anderson
2021-05-10 6:57 ` Leo Liang
2021-05-07 15:37 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2025-10-29 7:38 Leo Liang
2025-10-29 18:07 ` Tom Rini
2025-07-17 7:02 Leo Liang
2025-07-17 19:02 ` Tom Rini
2025-06-02 8:31 Leo Liang
2025-06-02 22:36 ` Tom Rini
2024-09-10 2:38 Leo Liang
2024-09-10 17:22 ` Tom Rini
2023-10-19 11:41 Leo Liang
2023-10-19 14:57 ` Tom Rini
2023-10-05 8:10 Leo Liang
2023-10-05 17:46 ` Tom Rini
2023-09-26 5:21 Leo Liang
2023-09-26 14:05 ` Tom Rini
2023-09-21 1:36 Leo Liang
2023-09-21 19:57 ` Tom Rini
2023-09-05 3:30 Leo Liang
2023-09-05 18:43 ` Tom Rini
2023-08-10 10:32 Leo Liang
2023-08-10 16:22 ` Tom Rini
2023-08-02 5:48 Leo Liang
2023-08-02 6:27 ` Bin Meng
2023-08-02 9:31 ` Leo Liang
2023-08-03 0:59 ` Minda Chen
2023-07-24 8:01 Leo Liang
2023-07-24 16:41 ` Tom Rini
2023-07-12 6:58 Leo Liang
2023-07-12 19:43 ` Tom Rini
2023-04-21 0:41 Leo Liang
2023-04-23 16:15 ` Tom Rini
2023-02-17 12:12 Leo Liang
2023-02-17 15:01 ` Tom Rini
2023-02-19 6:09 ` Leo Liang
2023-02-02 6:30 Leo Liang
2023-02-02 19:18 ` Tom Rini
2022-12-08 11:23 Leo Liang
2022-12-08 16:24 ` Tom Rini
2022-11-16 6:16 Leo Liang
2022-11-16 18:01 ` Tom Rini
2022-11-03 7:04 Leo Liang
2022-11-03 16:57 ` Tom Rini
2022-11-04 0:28 ` Leo Liang
2022-10-20 12:36 Leo Liang
2022-10-20 19:03 ` Tom Rini
2022-09-06 6:07 Leo Liang
2022-09-06 15:50 ` Tom Rini
2022-08-11 21:38 Leo Liang
2022-08-12 12:17 ` Tom Rini
2022-05-27 2:36 Leo Liang
2022-05-27 13:30 ` Tom Rini
2022-05-28 9:02 ` Leo Liang
2022-05-30 15:05 ` Tom Rini
2022-08-11 22:22 ` Leo Liang
2022-04-06 4:43 Leo Liang
2022-04-06 15:55 ` Tom Rini
2022-03-16 2:56 Leo Liang
2022-03-16 14:48 ` Tom Rini
2022-02-10 15:16 Leo Liang
2022-02-11 0:35 ` Tom Rini
2021-12-03 6:19 Leo Liang
2021-12-04 17:50 ` Tom Rini
2021-11-09 2:40 Leo Liang
2021-11-09 13:45 ` Tom Rini
2021-10-20 7:14 Leo Liang
2021-10-21 11:51 ` Tom Rini
2021-10-07 11:51 Leo Liang
2021-10-07 15:43 ` Tom Rini
2021-09-07 8:20 Leo Liang
2021-09-07 15:33 ` Tom Rini
2021-08-19 8:56 Leo Liang
2021-08-19 14:13 ` Tom Rini
2021-07-22 2:15 Leo Liang
2021-07-22 12:15 ` Tom Rini
2021-07-07 15:21 Leo Liang
2021-07-07 17:33 ` Tom Rini
2021-07-06 16:02 Leo Liang
2021-07-06 19:52 ` Tom Rini
2021-07-07 4:05 ` Tianrui Wei
2021-06-17 3:31 Leo Liang
2021-06-17 14:51 ` Tom Rini
2021-05-31 10:16 Leo Liang
2021-05-31 18:59 ` Tom Rini
2021-05-26 8:12 Leo Liang
2021-05-26 15:24 ` Tom Rini
2021-05-27 8:57 ` Green Wan
2021-05-27 10:41 ` Leo Liang
2021-05-27 11:20 ` Tom Rini
2021-05-27 13:56 ` Green Wan
2021-05-20 2:19 Leo Liang
2021-05-21 14:07 ` Tom Rini
2021-05-18 1:48 Leo Liang
2021-05-18 18:17 ` Tom Rini
2021-05-14 11:10 Leo Liang
2021-05-14 12:23 ` Bin Meng
2021-05-15 12:09 ` Tom Rini
2021-04-08 10:44 Leo Liang
2021-04-08 19:36 ` 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=20210507014136.GA16808@andestech.com \
--to=ycliang@andestech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.