mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Qingshuang Fu <fuqingshuang@kylinos.cn>
Cc: apw@canonical.com, joe@perches.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, shuah@kernel.org, willemb@google.com,
	littlesmilingcloud@gmail.com, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] selftests: net: fou_mcast_encap: load the fou module
Date: Tue, 22 Sep 2026 00:20:05 +0000	[thread overview]
Message-ID: <179003640515.3303074.9625403499092516237.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260917033049.792209-1-fuqingshuang@kylinos.cn>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 17 Sep 2026 11:30:49 +0800 you wrote:
> setup_ipv4() creates a GRETAP tunnel with FOU encap and configures a FOU
> port via "ip fou add". Both require the fou module, which cannot be
> auto-loaded.
> 
> The test assumes CONFIG_NET_FOU=y, which matches the default selftests
> config, but fails on kernels built with CONFIG_NET_FOU=m. Without the fou
> module, tunnel creation fails and the test reports a false failure with
> 0/100 received packets:
> 
> [...]

Here is the summary with links:
  - [net-next,v2] selftests: net: fou_mcast_encap: load the fou module
    https://git.kernel.org/netdev/net-next/c/6e0ee63cd2c9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-22  0:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17  3:30 Qingshuang Fu
2026-09-21  3:45 ` netdev-bot+sashiko
2026-09-22  2:10   ` Qingshuang Fu
2026-09-22  0:20 ` patchwork-bot+netdevbpf [this message]

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=179003640515.3303074.9625403499092516237.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=apw@canonical.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fuqingshuang@kylinos.cn \
    --cc=horms@kernel.org \
    --cc=joe@perches.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=littlesmilingcloud@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=willemb@google.com \
    /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
all inboxes | Powered by JetHome®