public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request: u-boot-riscv/master
Date: Thu, 4 Jun 2020 14:47:58 -0400	[thread overview]
Message-ID: <20200604184758.GH32287@bill-the-cat> (raw)
In-Reply-To: <c28bc13e-c71a-4807-8257-fb2d7e7a4ce3@ATCPCS12.andestech.com>

On Thu, Jun 04, 2020 at 10:18:07AM +0800, uboot at andestech.com wrote:

> Hi Tom,
> 
> Please pull some riscv updates:
> 
> - Fixes 7e249bc13aaf: ("riscv: Move all SMP related SBI calls to SBI_v01")
>    Move sbi_probe_extension() out of CONFIG_SBI_V01.
> - SiFive FU540 support SPL.
> 
> Thanks
> Rick
> 
> 
> https://travis-ci.org/github/rickchen36/u-boot-riscv/builds/694099665
> 
> 
> The following changes since commit 0d8f35b58cc8458a5263b424896a386429ee49e5:
> 
>   Merge https://gitlab.denx.de/u-boot/custodians/u-boot-spi (2020-06-03 12:27:51 -0400)
> 
> 	are available in the Git repository at:
> 
> 	  git at gitlab.denx.de:u-boot/custodians/u-boot-riscv.git
> 
> for you to fetch changes up to 0a94007e829876c7ebd49daebfaa90eea25801b8:
> 
>   riscv: sbi: Move sbi_probe_extension() out of CONFIG_SBI_V01 (2020-06-04 09:44:21 +0800)
> 

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200604/12cfc6df/attachment.sig>

  reply	other threads:[~2020-06-04 18:47 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04  2:18 [U-Boot] Pull request: u-boot-riscv/master uboot at andestech.com
2020-06-04 18:47 ` Tom Rini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-07-02  2:51 uboot at andestech.com
2020-07-02 13:53 ` Tom Rini
     [not found]   ` <752D002CFF5D0F4FA35C0100F1D73F3FA47207DF@ATCPCS16.andestech.com>
2020-07-03  6:01     ` Rick Chen
2020-07-03  6:52       ` Bin Meng
2020-06-24  2:30 uboot at andestech.com
2020-06-24  2:57 ` Bin Meng
     [not found]   ` <752D002CFF5D0F4FA35C0100F1D73F3FA471C57A@ATCPCS16.andestech.com>
2020-06-24  3:13     ` Rick Chen
2020-05-26  8:31 uboot at andestech.com
2020-05-26 19:55 ` Tom Rini
2020-05-25  8:01 uboot at andestech.com
2020-05-25 15:40 ` Tom Rini
     [not found]   ` <752D002CFF5D0F4FA35C0100F1D73F3FA470F21C@ATCPCS16.andestech.com>
2020-05-26  7:41     ` Rick Chen
2020-06-22  6:03     ` Rick Chen
2020-06-23  0:45       ` Tom Rini
2020-06-23  2:05         ` Rick Chen
2020-06-24  1:31         ` Rick Chen
2020-06-24  3:37           ` Sean Anderson
2020-04-23  8:25 uboot at andestech.com
2020-04-23 20:50 ` Tom Rini
2020-03-17  8:03 uboot at andestech.com
2020-03-18 13:56 ` Tom Rini
2020-02-10  7:29 uboot at andestech.com
2020-02-10 13:09 ` Tom Rini
2019-12-10  1:05 uboot at andestech.com
2019-12-10  4:01 ` Tom Rini
2019-10-18  7:00 uboot at andestech.com
2019-10-19 14:24 ` Tom Rini
2019-09-03  2:15 uboot at andestech.com
2019-09-04  0:58 ` Tom Rini
2019-08-26  8:25 uboot at andestech.com
2019-08-27  0:17 ` Tom Rini
2019-08-16  5:19 uboot at andestech.com
2019-08-17 17:47 ` Tom Rini
2019-08-12 10:23 uboot at andestech.com
2019-08-13 16:50 ` Tom Rini
     [not found]   ` <752D002CFF5D0F4FA35C0100F1D73F3FA40FF880@ATCPCS16.andestech.com>
2019-08-14  2:20     ` Rick Chen
2019-08-14 20:15       ` Auer, Lukas
2019-08-20 21:11         ` Auer, Lukas
2019-08-21  2:10           ` Rick Chen
2019-07-19  7:06 uboot at andestech.com
2019-07-23 13:46 ` Tom Rini
2019-06-05 10:27 uboot at andestech.com
2019-06-05 14:24 ` Tom Rini
2019-05-09  9:08 uboot at andestech.com
2019-05-09 22:25 ` Tom Rini
2019-04-08  6:46 uboot at andestech.com
2019-04-09 16:10 ` Tom Rini
2019-02-27  5:39 uboot at andestech.com
2019-02-28  3:59 ` Tom Rini
2019-01-15  7:16 uboot at andestech.com
2019-01-16 17:11 ` 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=20200604184758.GH32287@bill-the-cat \
    --to=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