From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10471] Building a mipsel kernel format vmlinuz (+ gzip + initrd) generates non-compressed, non-bootable image
Date: Wed, 10 Jan 2018 21:27:12 +0000 [thread overview]
Message-ID: <bug-10471-163-0NH1EQUgSx@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10471-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10471
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #9 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
The original contributor never came back with a way to reproduce the problem
with a reasonable kernel version (i.e not the Broadcom BSP), so let's mark the
bug as WONTFIX.
Do not hesitate to reopen with an easier way to reproduce the problem. Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2018-01-10 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 16:16 [Buildroot] [Bug 10471] New: Building a mipsel kernel format vmlinuz (+ gzip + initrd) generates non-compressed, non-bootable image bugzilla at busybox.net
2017-10-31 16:17 ` [Buildroot] [Bug 10471] " bugzilla at busybox.net
2017-10-31 16:27 ` bugzilla at busybox.net
2017-10-31 16:33 ` bugzilla at busybox.net
2017-10-31 16:34 ` bugzilla at busybox.net
2017-10-31 16:44 ` bugzilla at busybox.net
2017-10-31 16:45 ` bugzilla at busybox.net
2017-10-31 16:46 ` bugzilla at busybox.net
2017-10-31 21:01 ` bugzilla at busybox.net
2018-01-10 21:27 ` bugzilla at busybox.net [this message]
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-10471-163-0NH1EQUgSx@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 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.