From: patchwork-bot+netdevbpf@kernel.org
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: leon@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 iproute2 0/6] rdma: print related patches
Date: Sun, 07 Jan 2024 17:30:23 +0000 [thread overview]
Message-ID: <170464862399.7815.11969178755055314734.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240104011422.26736-1-stephen@networkplumber.org>
Hello:
This series was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Wed, 3 Jan 2024 17:13:38 -0800 you wrote:
> This set of patches makes rdma comman behave more like the
> other commands in iproute2 around printing flags.
> There are some other things found while looking at that code.
>
> This version keeps similar function names to original
>
> Stephen Hemminger (6):
> rdma: shorten print_ lines
> rdma: use standard flag for json
> rdma: make pretty behave like other commands
> rdma: make supress_errors a bit
> rdma: add oneline flag
> rdma: do not mix newline and json object
>
> [...]
Here is the summary with links:
- [v2,iproute2,1/6] rdma: shorten print_ lines
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=674e00aeaba7
- [v2,iproute2,2/6] rdma: use standard flag for json
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=22edc0cf37cd
- [v2,iproute2,3/6] rdma: make pretty behave like other commands
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=f962b24a5a33
- [v2,iproute2,4/6] rdma: make supress_errors a bit
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6e0d4e91a554
- [v2,iproute2,5/6] rdma: add oneline flag
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=27a477ba80da
- [v2,iproute2,6/6] rdma: do not mix newline and json object
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=a903854bad1c
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:[~2024-01-07 17:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 1:13 [PATCH v2 iproute2 0/6] rdma: print related patches Stephen Hemminger
2024-01-04 1:13 ` [PATCH v2 iproute2 1/6] rdma: shorten print_ lines Stephen Hemminger
2024-01-04 11:28 ` Petr Machata
2024-01-04 1:13 ` [PATCH v2 iproute2 2/6] rdma: use standard flag for json Stephen Hemminger
2024-01-04 12:07 ` Petr Machata
2024-01-04 1:13 ` [PATCH v2 iproute2 3/6] rdma: make pretty behave like other commands Stephen Hemminger
2024-01-04 1:13 ` [PATCH v2 iproute2 4/6] rdma: make supress_errors a bit Stephen Hemminger
2024-01-04 14:17 ` Petr Machata
2024-01-04 1:13 ` [PATCH v2 iproute2 5/6] rdma: add oneline flag Stephen Hemminger
2024-01-04 14:20 ` Petr Machata
2024-01-04 1:13 ` [PATCH v2 iproute2 6/6] rdma: do not mix newline and json object Stephen Hemminger
2024-01-04 14:29 ` Petr Machata
2024-01-04 5:58 ` [PATCH v2 iproute2 0/6] rdma: print related patches Chengchang Tang
2024-01-07 8:20 ` Leon Romanovsky
2024-01-07 17:30 ` 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=170464862399.7815.11969178755055314734.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--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).