All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Nicolas Escande <nico.escande@gmail.com>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org, idosch@idosch.org
Subject: Re: [iproute2,v2] man: bridge: update bridge link show
Date: Wed, 09 Aug 2023 20:50:20 +0000	[thread overview]
Message-ID: <169161422086.352.8750290247459279461.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230804164952.2649270-1-nico.escande@gmail.com>

Hello:

This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:

On Fri,  4 Aug 2023 18:49:52 +0200 you wrote:
> Add missing man page documentation for bridge link show features added in
> 13a5d8fcb41b (bridge: link: allow filtering on bridge name) and
> 64108901b737 (bridge: Add support for setting bridge port attributes)
> 
> Signed-off-by: Nicolas Escande <nico.escande@gmail.com>
> ---
>  man/man8/bridge.8 | 14 +++++++++++---
>  1 file changed, 11 insertions(+), 3 deletions(-)

Here is the summary with links:
  - [iproute2,v2] man: bridge: update bridge link show
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=cb93753e1042

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



      parent reply	other threads:[~2023-08-09 20:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 16:49 [iproute2,v2] man: bridge: update bridge link show Nicolas Escande
2023-08-08 11:36 ` Ido Schimmel
2023-08-09 16:12   ` Nicolas Escande
2023-08-10 15:00   ` Stephen Hemminger
2023-08-09 20:50 ` 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=169161422086.352.8750290247459279461.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=idosch@idosch.org \
    --cc=netdev@vger.kernel.org \
    --cc=nico.escande@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.