From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: forwarding: Add missing config entries
Date: Tue, 30 Jan 2024 13:00:27 +0000 [thread overview]
Message-ID: <170661962728.22779.7928925829236578595.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <025abded7ff9cea5874a7fe35dcd3fd41bf5e6ac.1706286755.git.petrm@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 26 Jan 2024 17:36:16 +0100 you wrote:
> The config file contains a partial kernel configuration to be used by
> `virtme-configkernel --custom'. The presumption is that the config file
> contains all Kconfig options needed by the selftests from the directory.
>
> In net/forwarding/config, many are missing, which manifests as spurious
> failures when running the selftests, with messages about unknown device
> types, qdisc kinds or classifier actions. Add the missing configurations.
>
> [...]
Here is the summary with links:
- [net-next] selftests: forwarding: Add missing config entries
https://git.kernel.org/netdev/net-next/c/4acf4e62cd57
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-01-30 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 16:36 [PATCH net-next] selftests: forwarding: Add missing config entries Petr Machata
2024-01-26 19:25 ` Jakub Kicinski
2024-01-29 10:45 ` Petr Machata
2024-01-30 2:31 ` Jakub Kicinski
2024-01-30 12:45 ` Paolo Abeni
2024-01-30 13:00 ` patchwork-bot+netdevbpf [this message]
2024-01-30 14:30 ` Jiri Pirko
2024-01-30 18:14 ` Jakub Kicinski
2024-02-13 17:17 ` Petr Machata
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=170661962728.22779.7928925829236578595.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.