From: patchwork-bot+netdevbpf@kernel.org
To: Martynas Pumputis <m@lambda.lt>
Cc: netdev@vger.kernel.org, edumazet@google.com,
daniel@iogearbox.net, ast@kernel.org, lmb@cloudflare.com
Subject: Re: [PATCH net-next v2 1/2] net: retrieve netns cookie via getsocketopt
Date: Thu, 24 Jun 2021 18:20:03 +0000 [thread overview]
Message-ID: <162455880386.31056.3165434549238056943.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210623135646.1632083-1-m@lambda.lt>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 23 Jun 2021 15:56:45 +0200 you wrote:
> It's getting more common to run nested container environments for
> testing cloud software. One of such examples is Kind [1] which runs a
> Kubernetes cluster in Docker containers on a single host. Each container
> acts as a Kubernetes node, and thus can run any Pod (aka container)
> inside the former. This approach simplifies testing a lot, as it
> eliminates complicated VM setups.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: retrieve netns cookie via getsocketopt
https://git.kernel.org/netdev/net-next/c/e8b9eab99232
- [net-next,v2,2/2] tools/testing: add a selftest for SO_NETNS_COOKIE
https://git.kernel.org/netdev/net-next/c/ae24bab257bb
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:[~2021-06-24 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 13:56 [PATCH net-next v2 1/2] net: retrieve netns cookie via getsocketopt Martynas Pumputis
2021-06-23 13:56 ` [PATCH net-next v2 2/2] tools/testing: add a selftest for SO_NETNS_COOKIE Martynas Pumputis
2021-06-23 14:07 ` [PATCH net-next v2 1/2] net: retrieve netns cookie via getsocketopt Eric Dumazet
2021-06-24 18: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=162455880386.31056.3165434549238056943.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=edumazet@google.com \
--cc=lmb@cloudflare.com \
--cc=m@lambda.lt \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).