From: patchwork-bot+netdevbpf@kernel.org
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
dsahern@gmail.com, simon.horman@corigine.com
Subject: Re: [PATCH iproute2 v3 0/2] iplink: update doc related to the 'netns' arg
Date: Sat, 22 Apr 2023 03:20:19 +0000 [thread overview]
Message-ID: <168213361911.18367.12559054475550059262.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230421074720.31004-1-nicolas.dichtel@6wind.com>
Hello:
This series was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Fri, 21 Apr 2023 09:47:18 +0200 you wrote:
> v2 -> v3:
> - make doc about netns arg consistent between 'add' and 'set'
>
> v1 -> v2:
> - add patch 1/2
> - s/NETNS_FILE/NETNSFILE
> - describe NETNSNAME in the DESCRIPTION section of man pages
>
> [...]
Here is the summary with links:
- [iproute2,v3,1/2] iplink: use the same token NETNSNAME everywhere
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=3921f56ec3be
- [iproute2,v3,2/2] iplink: fix help of 'netns' arg
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1371d7deaa20
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:[~2023-04-22 3:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 7:47 [PATCH iproute2 v3 0/2] iplink: update doc related to the 'netns' arg Nicolas Dichtel
2023-04-21 7:47 ` [PATCH iproute2 v3 1/2] iplink: use the same token NETNSNAME everywhere Nicolas Dichtel
2023-04-21 9:18 ` Simon Horman
2023-04-21 7:47 ` [PATCH iproute2 v3 2/2] iplink: fix help of 'netns' arg Nicolas Dichtel
2023-04-21 9:19 ` Simon Horman
2023-04-21 10:10 ` David Marchand
2023-04-21 10:53 ` [PATCH iproute2 v3 0/2] iplink: update doc related to the " Andrea Claudi
2023-04-22 3: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=168213361911.18367.12559054475550059262.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=simon.horman@corigine.com \
--cc=stephen@networkplumber.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).