Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, shuah@kernel.org, jiri@resnulli.us,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net] selftests: netdevsim: add a config file
Date: Thu, 18 Jan 2024 11:00:25 +0000	[thread overview]
Message-ID: <170557562555.29568.10174791710118557642.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240116154311.1945801-1-kuba@kernel.org>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue, 16 Jan 2024 07:43:11 -0800 you wrote:
> netdevsim tests aren't very well integrated with kselftest,
> which has its advantages and disadvantages. But regardless
> of the intended integration - a config file to know what kernel
> to build is very useful, add one.
> 
> Fixes: fc4c93f145d7 ("selftests: add basic netdevsim devlink flash testing")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> 
> [...]

Here is the summary with links:
  - [net] selftests: netdevsim: add a config file
    https://git.kernel.org/netdev/net/c/39369c9a6e09

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



      parent reply	other threads:[~2024-01-18 11:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 15:43 [PATCH net] selftests: netdevsim: add a config file Jakub Kicinski
2024-01-16 17:40 ` Paolo Abeni
2024-01-16 18:34   ` Jakub Kicinski
2024-01-17  9:32     ` Paolo Abeni
2024-01-17 15:39       ` Jakub Kicinski
2024-01-18 10:49         ` Paolo Abeni
2024-01-18 11:00 ` 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=170557562555.29568.10174791710118557642.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.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