From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15952] Grub fails to load large rootfs files
Date: Tue, 20 Feb 2024 16:27:14 +0000 [thread overview]
Message-ID: <bug-15952-163-D2ZVQPWSMK@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15952-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15952
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
CC| |yann.morin.1998@free.fr
Status|NEW |RESOLVED
--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Dr I J Ormshaw, All,
This is a grub limitation, so please work with grub upstream to lift that
limitation. Once they have accepted a fix, then we can see whether we can
backport it or not.
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-02-20 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 11:33 [Buildroot] [Bug 15952] New: Grub fails to load large rootfs files bugzilla
2024-02-20 11:36 ` [Buildroot] [Bug 15952] " bugzilla
2024-02-20 16:27 ` bugzilla [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-15952-163-D2ZVQPWSMK@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox