From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13536] Build issues and workarounds with qemu_aarch64_virt_defconfig
Date: Thu, 18 Feb 2021 20:35:07 +0000 [thread overview]
Message-ID: <bug-13536-163-aN9VLhCVbg@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13536-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13536
--- Comment #2 from Jarkko Sakkinen <jarkko.sakkinen@iki.fi> ---
(In reply to Thomas Petazzoni from comment #1)
Thanks I can do that.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-18 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 1:03 [Buildroot] [Bug 13536] New: Build issues and workarounds with qemu_aarch64_virt_defconfig bugzilla at busybox.net
2021-02-16 21:26 ` [Buildroot] [Bug 13536] " bugzilla at busybox.net
2021-02-18 20:35 ` bugzilla at busybox.net [this message]
2024-06-15 14:56 ` bugzilla
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=bug-13536-163-aN9VLhCVbg@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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