From: patchwork-bot+netdevbpf@kernel.org
To: Bobby Eshleman <bobbyeshleman@gmail.com>
Cc: sgarzare@redhat.com, shuah@kernel.org,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
kuba@kernel.org, bobbyeshleman@meta.com
Subject: Re: [PATCH net-next v2] selftests/vsock: auto-detect kernel for guest VMs
Date: Thu, 19 Mar 2026 03:10:14 +0000 [thread overview]
Message-ID: <177388981428.1008325.4813735802050665740.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260316-vsock-vmtest-autodetect-kernel-v2-1-5eec7b4831f8@meta.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 16 Mar 2026 17:56:15 -0700 you wrote:
> From: Bobby Eshleman <bobbyeshleman@meta.com>
>
> When running vmtest.sh inside a nested VM the running kernel may not be
> installed on the filesystem at the standard /boot/ or /usr/lib/modules/
> paths.
>
> Previously, this would cause vng to fail with "does not exist" since it
> could not find the kernel image. Instead, this patch uses --dry-run to
> detect if the kernel is available. If not, then we fall back to the
> kernel in the kernel source tree. If that fails, then we die.
>
> [...]
Here is the summary with links:
- [net-next,v2] selftests/vsock: auto-detect kernel for guest VMs
https://git.kernel.org/netdev/net-next/c/3883c2b50910
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-19 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 0:56 [PATCH net-next v2] selftests/vsock: auto-detect kernel for guest VMs Bobby Eshleman
2026-03-19 3:10 ` 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=177388981428.1008325.4813735802050665740.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bobbyeshleman@gmail.com \
--cc=bobbyeshleman@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=shuah@kernel.org \
--cc=virtualization@lists.linux.dev \
/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