From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] Dockerfile: build GRUB UEFI target for RISC-V 64bit
Date: Thu, 12 Sep 2019 17:17:20 -0400 [thread overview]
Message-ID: <20190912211720.GL6927@bill-the-cat> (raw)
In-Reply-To: <aeee39a4-06aa-7a91-fa55-3a098a260b3a@gmx.de>
On Thu, Sep 12, 2019 at 10:31:39PM +0200, Heinrich Schuchardt wrote:
> On 8/4/19 3:31 PM, Bin Meng wrote:
> >On Sun, Aug 4, 2019 at 8:10 PM Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> >>
> >>Build GRUB UEFI target grubriscv64.efi. It is needed for running
> >>test_efi_grub_net().
> >>
> >>Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> >>---
> >>This patch applies to
> >>https://gitlab.denx.de/u-boot/gitlab-ci-runner
> >>---
> >> Dockerfile | 14 ++++++++++++++
> >> 1 file changed, 14 insertions(+)
> >>
> >
> >Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
> >_______________________________________________
> >U-Boot mailing list
> >U-Boot at lists.denx.de
> >https://lists.denx.de/listinfo/u-boot
> >
> Hello Tom,
>
> the patch did not yet make it into
>
> https://gitlab.denx.de/u-boot/gitlab-ci-runner.git
>
> Anything I should do?
Sorry, I assume this is blocking being able to then enable tests on the
platform? If so, I'll go spin things around shortly and in the future
feel free to poke me if I don't turn them around in a day or two.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190912/01e29679/attachment.sig>
next prev parent reply other threads:[~2019-09-12 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 12:10 [U-Boot] [PATCH 1/1] Dockerfile: build GRUB UEFI target for RISC-V 64bit Heinrich Schuchardt
2019-08-04 13:31 ` Bin Meng
2019-09-12 20:31 ` Heinrich Schuchardt
2019-09-12 21:17 ` Tom Rini [this message]
2019-09-13 11:24 ` Heinrich Schuchardt
2019-09-13 14:06 ` 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=20190912211720.GL6927@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