From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/2021.2 v1] package/genimage: fix for WSL (Windows-Subsystem for Linux)
Date: Sun, 14 Mar 2021 23:43:56 +0100 [thread overview]
Message-ID: <20210314234356.27b5ae4b@gmx.net> (raw)
In-Reply-To: <20210314231951.092ee00a@windsurf.home>
Hello Thomas,
On Sun, 14 Mar 2021 23:19:51 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello Peter,
>
> On Wed, 10 Mar 2021 20:16:51 +0100
> Peter Seiderer <ps.report@gmx.net> wrote:
>
> > - add upstream patch ([1]) to fix usage with WSL (Windows-Subsystem for Linux)
> >
> > Fixes:
> >
> > - https://bugs.busybox.net/show_bug.cgi?id=13146
> > - https://bugs.busybox.net/show_bug.cgi?id=13601
> >
> > ERROR: hdimage(sdcard.img): fiemap .../images/boot.vfat: 25 Inappropriate ioctl for device
> > ERROR: hdimage(sdcard.img): failed to write image partition 'boot'
> >
> > [1] https://github.com/pengutronix/genimage/commit/4c2b02df0861e06ca9320d80ad60994d4a239ad6.patch
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> You tagged this patch 2021.02. Does this mean that:
>
> - It should be applied *only* for 2021.02, and not master? If so, for
> what reason?
On master genimage version is already bumped to 14 (containing the
upstream patch already)..., on 2021.02 genimage is still on version
13...
Regards,
Peter
>
> - It should be applied to both 2021.02 and master ?
>
> Thanks for having investigated this, just this week, I had a
> participant to my training course running under WSL2 who faced exactly
> that issue.
>
> Best regards,
>
> Thomas
next prev parent reply other threads:[~2021-03-14 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 19:16 [Buildroot] [PATCH/2021.2 v1] package/genimage: fix for WSL (Windows-Subsystem for Linux) Peter Seiderer
2021-03-10 22:33 ` Yann E. MORIN
2021-03-14 22:19 ` Thomas Petazzoni
2021-03-14 22:43 ` Peter Seiderer [this message]
2021-04-07 9:07 ` Peter Korsgaard
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=20210314234356.27b5ae4b@gmx.net \
--to=ps.report@gmx.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