From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Artemii Morozov <artemii.morozov@arknetworks.am>, dev@dpdk.org
Cc: Ivan Malov <ivan.malov@arknetworks.am>,
Viacheslav Galaktionov <viacheslav.galaktionov@arknetworks.am>,
Andy Moreton <amoreton@xilinx.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [PATCH 0/2] support IPv4 fragment matching in transfer rules
Date: Tue, 27 Jun 2023 15:02:14 +0100 [thread overview]
Message-ID: <1fac493a-ec21-d87e-f86c-c89791007ad7@amd.com> (raw)
In-Reply-To: <20230623165824.51908-1-artemii.morozov@arknetworks.am>
On 6/23/2023 5:58 PM, Artemii Morozov wrote:
> This patch seria adds support for matching fragment offsets for IPv4 packets,
> but with some limitations. Exact matching is supported only for zero offset,
> ranges are allowed for non-zero offsets.
>
> Artemii Morozov (2):
> common/sfc_efx/base: add MAE IP fragmentation match bits
> net/sfc: support IPv4 fragment matching in transfer rules
>
Hi Artemii,
There is a build error, can you please fix it:
../drivers/net/sfc/sfc_mae.c: In function ‘sfc_mae_rule_parse_item_ipv4’:
../drivers/net/sfc/sfc_mae.c:2335:22: error: assignment discards ‘const’
qualifier from pointer target type [-Werror=discarded-qualifiers]
2335 | last = item->last;
| ^
cc1: all warnings being treated as errors
next prev parent reply other threads:[~2023-06-27 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 16:58 Artemii Morozov
2023-06-23 16:58 ` [PATCH 1/2] common/sfc_efx/base: add MAE IP fragmentation match bits Artemii Morozov
2023-06-23 16:58 ` [PATCH 2/2] net/sfc: support IPv4 fragment matching in transfer rules Artemii Morozov
2023-06-27 14:02 ` Ferruh Yigit [this message]
2023-06-28 7:00 ` [PATCH v2 0/2] " Artemii Morozov
2023-06-28 7:00 ` [PATCH v2 1/2] common/sfc_efx/base: add MAE IP fragmentation match bits Artemii Morozov
2023-06-28 7:00 ` [PATCH v2 2/2] net/sfc: support IPv4 fragment matching in transfer rules Artemii Morozov
2023-06-28 10:53 ` [PATCH v2 0/2] " Ferruh Yigit
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=1fac493a-ec21-d87e-f86c-c89791007ad7@amd.com \
--to=ferruh.yigit@amd.com \
--cc=amoreton@xilinx.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=artemii.morozov@arknetworks.am \
--cc=dev@dpdk.org \
--cc=ivan.malov@arknetworks.am \
--cc=viacheslav.galaktionov@arknetworks.am \
/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).