From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: Pull request v2: u-boot-spi/master
Date: Tue, 28 Apr 2020 15:21:53 -0400 [thread overview]
Message-ID: <20200428192153.GF4468@bill-the-cat> (raw)
In-Reply-To: <20200428122800.4416-1-jagan@amarulasolutions.com>
On Tue, Apr 28, 2020 at 05:58:00PM +0530, Jagan Teki wrote:
> Hi Tom,
>
> Please pull this PR.
>
> Travis-ci:
> https://travis-ci.org/github/openedev/u-boot-amarula/builds/680186752
>
> Changes for v2:
> - included SiFive SPI fixes
> - fixes for SF distro on rockchip
>
> thanks,
> Jagan.
>
> The following changes since commit 8d5d3bcf3c53d798bd7f3fe7092e994593bcc41c:
>
> Merge branch '2020-04-16-master-imports' (2020-04-17 11:17:29 -0400)
>
> are available in the Git repository at:
>
> https://gitlab.denx.de/u-boot/custodians/u-boot-spi master
>
> for you to fetch changes up to 96955bbb077256db9f56c06b4983810237d700a4:
>
> sifive: fu540: Enable spi-nor flash support (2020-04-28 15:32:00 +0530)
>
This still fails to build a lot of platforms as:
https://travis-ci.org/github/trini/u-boot/jobs/680641434
Which is like before, but I see you have passing travis jobs. I also
see that it's not for 96955bbb077256db9f56c06b4983810237d700a4 which is
what I get on fetching the spi repo. Please figure out where the good
revision went :) 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/20200428/5c9f2d53/attachment.sig>
next prev parent reply other threads:[~2020-04-28 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 12:28 Pull request v2: u-boot-spi/master Jagan Teki
2020-04-28 19:21 ` Tom Rini [this message]
2020-04-28 19:32 ` Jagan Teki
-- strict thread matches above, loose matches on Subject: below --
2020-05-10 20:07 Jagan Teki
2020-05-11 13:46 ` 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=20200428192153.GF4468@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 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.