From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13601] Gen image :Iappropriate ioctl error
Date: Tue, 09 Mar 2021 20:45:59 +0000 [thread overview]
Message-ID: <bug-13601-163-6hnZ9l1ZEf@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13601-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13601
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr
--- Comment #3 from Yann E. MORIN <yann.morin.1998@free.fr> ---
(In reply to Peter Seiderer from comment #2)
> similar/same failure was already reported, see #13146
But 13146 was about WSL1, no? That error is not supposed to hapen under WSL2,
as I understand it...
NirajTummala, are you sure you are using WSL2? Care to double-check, please?
> latest genimage version bump (see [3]), not yet in 2021.02, only on git master...
Could you please send a patch for 2021.02 with just a backport of that fix,
please?
(yes, I know I was not in favour of it back then, but since upstream did apply
it, then we can backport it now).
Thanks!
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-09 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 15:31 [Buildroot] [Bug 13601] New: Gen image :Iappropriate ioctl error bugzilla at busybox.net
2021-03-09 15:37 ` [Buildroot] [Bug 13601] " bugzilla at busybox.net
2021-03-09 20:15 ` bugzilla at busybox.net
2021-03-09 20:45 ` bugzilla at busybox.net [this message]
2021-03-09 20:49 ` bugzilla at busybox.net
2021-03-10 19:19 ` bugzilla at busybox.net
2021-03-22 15:34 ` bugzilla at busybox.net
2021-04-07 9:12 ` bugzilla at busybox.net
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-13601-163-6hnZ9l1ZEf@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