From: Andrea Righi <arighi@nvidia.com>
To: Matthieu Baerts <matttbe@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: torvalds@linux-foundation.org, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
pabeni@redhat.com, Guo Weikang <guoweikang.kernel@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [GIT PULL] Networking for v6.13-rc7
Date: Fri, 24 Jan 2025 19:07:08 +0100 [thread overview]
Message-ID: <Z5PWzNYxJAYjbJkv@gpd3> (raw)
In-Reply-To: <426d4476-e3b4-4a95-84a1-850015651ee6@kernel.org>
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
next prev parent reply other threads:[~2025-01-24 18:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 18:29 [GIT PULL] Networking for v6.13-rc7 Jakub Kicinski
2025-01-09 23:21 ` pr-tracker-bot
2025-01-17 3:38 ` Jakub Kicinski
2025-01-18 13:45 ` Catalin Marinas
2025-01-20 14:51 ` Catalin Marinas
2025-01-20 17:45 ` Jakub Kicinski
2025-01-21 11:09 ` Catalin Marinas
2025-01-21 15:42 ` Jakub Kicinski
2025-01-21 20:46 ` Catalin Marinas
2025-01-23 17:11 ` Matthieu Baerts
2025-01-24 18:07 ` Andrea Righi [this message]
2025-01-27 14:27 ` Catalin Marinas
2025-01-27 17:39 ` Matthieu Baerts
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=Z5PWzNYxJAYjbJkv@gpd3 \
--to=arighi@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=guoweikang.kernel@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).