From: Ido Schimmel <idosch@idosch•org>
To: Zahari Doychev <zahari.doychev@linux•com>
Cc: netdev@vger•kernel.org, jhs@mojatatu•com,
xiyou.wangcong@gmail•com, jiri@resnulli•us, davem@davemloft•net,
edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
hmehrtens@maxlinear•com, aleksander.lobakin@intel•com,
simon.horman@corigine•com,
Zahari Doychev <zdoychev@maxlinear•com>
Subject: Re: [PATCH net-next v5 1/3] net: flow_dissector: add support for cfm packets
Date: Mon, 5 Jun 2023 10:21:46 +0300 [thread overview]
Message-ID: <ZH2NCmmORVfhdpTl@shredder> (raw)
In-Reply-To: <20230604115825.2739031-2-zahari.doychev@linux.com>
On Sun, Jun 04, 2023 at 01:58:23PM +0200, Zahari Doychev wrote:
> From: Zahari Doychev <zdoychev@maxlinear•com>
>
> Add support for dissecting cfm packets. The cfm packet header
> fields maintenance domain level and opcode can be dissected.
>
> Signed-off-by: Zahari Doychev <zdoychev@maxlinear•com>
> Reviewed-by: Simon Horman <simon.horman@corigine•com>
Reviewed-by: Ido Schimmel <idosch@nvidia•com>
next prev parent reply other threads:[~2023-06-05 7:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 11:58 [PATCH net-next v5 0/3] net: flower: add cfm support Zahari Doychev
2023-06-04 11:58 ` [PATCH net-next v5 1/3] net: flow_dissector: add support for cfm packets Zahari Doychev
2023-06-05 7:21 ` Ido Schimmel [this message]
2023-06-04 11:58 ` [PATCH net-next v5 2/3] net: flower: add support for matching cfm fields Zahari Doychev
2023-06-05 7:36 ` Ido Schimmel
2023-06-06 14:37 ` Zahari Doychev
2023-06-04 11:58 ` [PATCH net-next v5 3/3] selftests: net: add tc flower cfm test Zahari Doychev
2023-06-05 7:42 ` Ido Schimmel
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=ZH2NCmmORVfhdpTl@shredder \
--to=idosch@idosch$(echo .)org \
--cc=aleksander.lobakin@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hmehrtens@maxlinear$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=simon.horman@corigine$(echo .)com \
--cc=xiyou.wangcong@gmail$(echo .)com \
--cc=zahari.doychev@linux$(echo .)com \
--cc=zdoychev@maxlinear$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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