From: Jakub Kicinski <kuba@kernel.org>
To: <edward.cree@amd.com>
Cc: <linux-net-drivers@amd.com>, <davem@davemloft.net>,
<pabeni@redhat.com>, <edumazet@google.com>,
Edward Cree <ecree.xilinx@gmail.com>, <netdev@vger.kernel.org>,
<habetsm.xilinx@gmail.com>,
Pieter Jansen van Vuuren <pieter.jansen-van-vuuren@amd.com>
Subject: Re: [PATCH net-next 2/4] sfc: populate enc_ip_tos matches in MAE outer rules
Date: Fri, 21 Apr 2023 21:04:16 -0700 [thread overview]
Message-ID: <20230421210416.5a80e25f@kernel.org> (raw)
In-Reply-To: <d1fd9a055378a5e0f969d0ecb69ca2a4cd8257bb.1682086533.git.ecree.xilinx@gmail.com>
On Fri, 21 Apr 2023 15:19:52 +0100 edward.cree@amd.com wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> Currently tc.c will block them before they get here, but following
> patch will change that.
> Use the extack message from efx_mae_check_encap_match_caps() instead
> of writing a new one, since there's now more being fed in than just
> an IP version.
Transient build breakage here
--
pw-bot: cr
next prev parent reply other threads:[~2023-04-22 4:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 14:19 [PATCH net-next 0/4] sfc: more flexible encap matches on TC decap rules edward.cree
2023-04-21 14:19 ` [PATCH net-next 1/4] sfc: release encap match in efx_tc_flow_free() edward.cree
2023-04-21 14:19 ` [PATCH net-next 2/4] sfc: populate enc_ip_tos matches in MAE outer rules edward.cree
2023-04-22 4:04 ` Jakub Kicinski [this message]
2023-04-24 11:04 ` Edward Cree
2023-04-21 14:19 ` [PATCH net-next 3/4] sfc: support TC decap rules matching on enc_ip_tos edward.cree
2023-04-21 14:19 ` [PATCH net-next 4/4] sfc: support TC decap rules matching on enc_src_port edward.cree
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=20230421210416.5a80e25f@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pieter.jansen-van-vuuren@amd.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 NNTP newsgroup(s).