From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request: u-boot-riscv/master
Date: Mon, 25 May 2020 11:40:05 -0400 [thread overview]
Message-ID: <20200525154005.GS26741@bill-the-cat> (raw)
In-Reply-To: <2e5a5174-9872-4413-85b0-aa9f1ff446fa@ATCPCS12.andestech.com>
On Mon, May 25, 2020 at 04:01:08PM +0800, uboot at andestech.com wrote:
> Hi Tom,
>
> Please pull some riscv updates:
>
> - Add Sipeed Maix support.
> - sifive: fix palmer's email address.
> - Move all SMP related SBI calls to SBI_v01.
>
> https://travis-ci.org/github/rickchen36/u-boot-riscv/builds/690778926
>
> Thanks
> Rick
>
>
> The following changes since commit 9c5fef577494769e3ff07952a85f9b7125ef765b:
>
> Merge git://git.denx.de/u-boot-usb (2020-05-22 22:58:50 -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 421c4eb2dcf39f65c31c1804369267ed8a7b5607:
>
> riscv: Add Sipeed Maix support (2020-05-25 10:01:21 +0800)
>
There's too many generic changes in this PR for this late in the cycle,
for things I gather related to the Maix platform. All of the clk and DM
changes impact virtually all platforms. Please re-do this PR to drop
the Maix platform support for now, and resubmit that for -next, which I
will be opening shortly. Everything else however is good for master.
Sorry.
--
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/20200525/9b8498d6/attachment.sig>
next prev parent reply other threads:[~2020-05-25 15:40 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 8:01 [U-Boot] Pull request: u-boot-riscv/master uboot at andestech.com
2020-05-25 15:40 ` Tom Rini [this message]
[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
-- 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-06-04 2:18 uboot at andestech.com
2020-06-04 18:47 ` Tom Rini
2020-05-26 8:31 uboot at andestech.com
2020-05-26 19:55 ` Tom Rini
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=20200525154005.GS26741@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