Re: [PATCH] scripts/qemu-binfmt-conf.sh: refresh

2024-02-24 Thread Michael Tokarev
23.02.2024 18:55, Peter Maydell: On Sun, 18 Feb 2024 at 09:32, Michael Tokarev wrote: 09.09.2023 16:23, Michael Tokarev : A friendly ping? A friendly ping #2? Looking at the patch, the commit message lists 9 separate things it does. That suggests it ought to be a 9-patch patchset, not a

Re: [PATCH] scripts/qemu-binfmt-conf.sh: refresh

2024-02-23 Thread Peter Maydell
On Sun, 18 Feb 2024 at 09:32, Michael Tokarev wrote: > > 09.09.2023 16:23, Michael Tokarev : > > A friendly ping? > > A friendly ping #2? Looking at the patch, the commit message lists 9 separate things it does. That suggests it ought to be a 9-patch patchset, not a single patch. I bet most of

Re: [PATCH] scripts/qemu-binfmt-conf.sh: refresh

2024-02-18 Thread Michael Tokarev
09.09.2023 16:23, Michael Tokarev : A friendly ping? A friendly ping #2? Thanks, /mjt 21.07.2023 14:50, Michael Tokarev wrote: Currently qemu-binfmt-conf.sh does a number of strange things. 1. --systemd requires an argument - the CPU type to register,     while --debian (which is

Re: [PATCH] scripts/qemu-binfmt-conf.sh: refresh

2023-09-09 Thread Michael Tokarev
A friendly ping? Thanks, /mjt 21.07.2023 14:50, Michael Tokarev wrote: Currently qemu-binfmt-conf.sh does a number of strange things. 1. --systemd requires an argument - the CPU type to register, while --debian (which is actually --binfmt-support) does not accept such an argument, so

[PATCH] scripts/qemu-binfmt-conf.sh: refresh

2023-07-21 Thread Michael Tokarev
Currently qemu-binfmt-conf.sh does a number of strange things. 1. --systemd requires an argument - the CPU type to register, while --debian (which is actually --binfmt-support) does not accept such an argument, so it is not possible to specify which CPU(s) to register for debian. 2. Why