[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z5PWzNYxJAYjbJkv@gpd3>
Date: Fri, 24 Jan 2025 19:07:08 +0100
From: Andrea Righi <arighi@...dia.com>
To: Matthieu Baerts <matttbe@...nel.org>,
Catalin Marinas <catalin.marinas@....com>
Cc: torvalds@...ux-foundation.org, davem@...emloft.net,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
pabeni@...hat.com, Guo Weikang <guoweikang.kernel@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jakub Kicinski <kuba@...nel.org>
Subject: Re: [GIT PULL] Networking for v6.13-rc7
On Thu, Jan 23, 2025 at 06:11:16PM +0100, Matthieu Baerts wrote:
...
> Please note that on our side with MPTCP, I can only reproduce this issue
> locally, but not from our CI on GitHub Actions. The main difference is
> the kernel (6.8 on the CI, 6.12 here) and the fact our CI is launching
> virtme-ng from a VM. The rest should be the same.
>
> > (after hacking vng to allow x86_64 as non-host architecture).
Ah right, we still don't support `--arch x86_64|amd64`, it's definitely
something we should add.
>
> Do not hesitate to report this issue + hack on vng's bug tracker :)
>
> https://github.com/arighi/virtme-ng/issues/new
Yep, as pointed by Matt, feel free to post your hack there, otherwise I'll
take a look at this.
Thanks,
-Andrea
Powered by blists - more mailing lists