From: patchwork-bot+netdevbpf@kernel.org
To: Leo Yan <leo.yan@linaro.org>
Cc: davem@davemloft.net, kuba@kernel.org, suzuki.poulose@arm.com,
leon@kernel.org, bsingharora@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/2] pid: Introduce helper task_is_in_root_ns()
Date: Thu, 27 Jan 2022 03:10:10 +0000 [thread overview]
Message-ID: <164325301030.26280.5565890231201781170.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220126050427.605628-1-leo.yan@linaro.org>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 26 Jan 2022 13:04:25 +0800 you wrote:
> This patch series introduces a helper function task_is_in_init_pid_ns()
> to replace open code. The two patches are extracted from the original
> series [1] for network subsystem.
>
> As a plan, we can firstly land this patch set into kernel 5.18; there
> have 5 patches are left out from original series [1], as a next step,
> I will resend them for appropriate linux-next merging.
>
> [...]
Here is the summary with links:
- [net,v3,1/2] pid: Introduce helper task_is_in_init_pid_ns()
https://git.kernel.org/netdev/net/c/d7e4f8545b49
- [net,v3,2/2] connector/cn_proc: Use task_is_in_init_pid_ns()
https://git.kernel.org/netdev/net/c/42c66d167564
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:[~2022-01-27 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 5:04 [PATCH net v3 0/2] pid: Introduce helper task_is_in_root_ns() Leo Yan
2022-01-26 5:04 ` [PATCH net v3 1/2] pid: Introduce helper task_is_in_init_pid_ns() Leo Yan
2022-01-26 5:04 ` [PATCH net v3 2/2] connector/cn_proc: Use task_is_in_init_pid_ns() Leo Yan
2022-01-27 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=164325301030.26280.5565890231201781170.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bsingharora@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=leo.yan@linaro.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=suzuki.poulose@arm.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;
as well as URLs for NNTP newsgroup(s).