From: Date Huang <tjjh89017@hotmail.com>
To: roopa@nvidia.com, razor@blackwall.org, jiri@resnulli.us
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
tjjh89017@hotmail.com
Subject: [PATCH iproute2-next v2 0/2] bridge: vlan: add compressvlans manpage
Date: Fri, 22 Mar 2024 20:39:21 +0800 [thread overview]
Message-ID: <MAZP287MB05039AA2ECF8022DD501D4BCE4312@MAZP287MB0503.INDP287.PROD.OUTLOOK.COM> (raw)
Hi maintainers
I followed Nikolay and Jiri's comment and updated the patch to v2.
Please check it.
Date Huang (2):
bridge: vlan: fix compressvlans usage
bridge: vlan: add compressvlans manpage
bridge/bridge.c | 2 +-
man/man8/bridge.8 | 6 ++++++
2 files changed, 7 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2024-03-22 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 12:39 Date Huang [this message]
2024-03-22 12:58 ` [PATCH iproute2-next v2 0/2] bridge: vlan: add compressvlans manpage Nikolay Aleksandrov
2024-03-26 17:20 ` patchwork-bot+netdevbpf
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=MAZP287MB05039AA2ECF8022DD501D4BCE4312@MAZP287MB0503.INDP287.PROD.OUTLOOK.COM \
--to=tjjh89017@hotmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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 read-only IMAP folder(s) and NNTP newsgroup(s).