From: patchwork-bot+netdevbpf@kernel.org
To: Zahari Doychev <zahari.doychev@linux.com>
Cc: netdev@vger.kernel.org, dsahern@gmail.com,
stephen@networkplumber.org, hmehrtens@maxlinear.com,
aleksander.lobakin@intel.com, simon.horman@corigine.com,
idosch@idosch.org, zdoychev@maxlinear.com
Subject: Re: [PATCH iproute2-next] f_flower: simplify cfm dump function
Date: Mon, 03 Jul 2023 16:10:20 +0000 [thread overview]
Message-ID: <168840062073.14655.17510773342948225363.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230629195736.675018-1-zahari.doychev@linux.com>
Hello:
This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Thu, 29 Jun 2023 21:57:36 +0200 you wrote:
> From: Zahari Doychev <zdoychev@maxlinear.com>
>
> The standard print function can be used to print the cfm attributes in
> both standard and json use cases. In this way no string buffer is needed
> which simplifies the code.
>
> Signed-off-by: Zahari Doychev <zdoychev@maxlinear.com>
>
> [...]
Here is the summary with links:
- [iproute2-next] f_flower: simplify cfm dump function
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=19f44c06e5e2
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-07-03 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 19:57 [PATCH iproute2-next] f_flower: simplify cfm dump function Zahari Doychev
2023-06-30 11:22 ` Petr Machata
2023-06-30 19:37 ` Zahari Doychev
2023-06-30 21:17 ` Stephen Hemminger
2023-07-03 8:01 ` Ido Schimmel
2023-07-03 16: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=168840062073.14655.17510773342948225363.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=dsahern@gmail.com \
--cc=hmehrtens@maxlinear.com \
--cc=idosch@idosch.org \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@corigine.com \
--cc=stephen@networkplumber.org \
--cc=zahari.doychev@linux.com \
--cc=zdoychev@maxlinear.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 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.