From: "prince.yh.kuo" <prince.yh.kuo@aewin.com>
To: "'Andrew Geissler'" <geissonator@gmail.com>
Cc: openbmc@lists.ozlabs.org
Subject: RE: [OpenBMC] - QEMU link seem like can't download
Date: Thu, 28 Jan 2021 08:47:50 +0800 [thread overview]
Message-ID: <000301d6f50f$346afe30$9d40fa90$@yh.kuo@aewin.com> (raw)
In-Reply-To: <1A168CFD-4555-4E27-8E25-466D6243854A@gmail.com>
Hi Andrew,
Thanks for your reply.
Have a nice day :)
Many thanks
Prince
-----Original Message-----
From: Andrew Geissler [mailto:geissonator@gmail.com]
Sent: Wednesday, January 27, 2021 10:48 AM
To: prince.yh.kuo
Cc: openbmc@lists.ozlabs.org
Subject: Re: [OpenBMC] - QEMU link seem like can't download
> On Jan 21, 2021, at 4:31 AM, prince.yh.kuo <prince.yh.kuo@aewin.com> wrote:
>
> Hi,
> I’m a beginner of OpenBMC and I found QEMU link seem like can’t download, is right?
> <image001.jpg>
Thanks for pointing this out. The build env changed recently and that resulted in
a different link for this tool.
I put a doc fix up at https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/40033
New link for tool is https://jenkins.openbmc.org/job/latest-qemu-x86/lastSuccessfulBuild/artifact/qemu/build/qemu-system-arm
> Regards,
> Prince
>
> 郭育宏(Prince Kuo)
> 其陽科技股份有限公司
> AEWIN Technology Co.,Ltd
> 新北市汐止區大同路二段133號9樓
> 9F., No.133, Sec. 2, Datung Rd., Xizhi Dist., New Taipei City 22101, Taiwan
> Email : prince.yh.kuo@aewin.com.tw
> TEL : +886-2-8692-6677 ext 9307
> FAX : +886-2-8692-6655
next prev parent reply other threads:[~2021-01-28 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6010b181.1c69fb81.7b936.e70fSMTPIN_ADDED_BROKEN@mx.google.com>
2021-01-27 2:47 ` [OpenBMC] - QEMU link seem like can't download Andrew Geissler
2021-01-28 0:47 ` prince.yh.kuo [this message]
2021-01-21 10:31 prince.yh.kuo
2021-01-27 1:58 ` Andrew Jeffery
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='000301d6f50f$346afe30$9d40fa90$@yh.kuo@aewin.com' \
--to=prince.yh.kuo@aewin.com \
--cc=geissonator@gmail.com \
--cc=openbmc@lists.ozlabs.org \
/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.