From: Stephen Hemminger <stephen@networkplumber.org>
To: Serhii Iliushyk <sil-plv@napatech.com>
Cc: dev@dpdk.org, mko-plv@napatech.com, ckm@napatech.com,
andrew.rybchenko@oktetlabs.ru, ferruh.yigit@amd.com
Subject: Re: [PATCH v1 0/3] Bugfixes
Date: Sun, 24 Nov 2024 10:12:46 -0800 [thread overview]
Message-ID: <20241124101246.0b640966@hermes.local> (raw)
In-Reply-To: <20241120180258.64185-1-sil-plv@napatech.com>
On Wed, 20 Nov 2024 19:02:54 +0100
Serhii Iliushyk <sil-plv@napatech.com> wrote:
> This patch set provides further fixes:
>
> Feature DSCP:
> The issue with the modification of the DSCP field
> for IPV4 and IPV6 is fixed by adding
> copying the DSCP value to the flow handler.
>
> Feature MTU:
> Supplement existing toggle-like macros
> with respective opposites for the correct enablement of the MTU
>
> The header rte_pmd_ntnic.h was moved
> to the root of ntnic PMD. The correct place for this header.
>
> Danylo Vodopianov (1):
> net/ntnic: fix action modify field DSCP
>
> Oleksandr Kolomeiets (2):
> net/ntnic: add supplementary macros
> net/ntnic: move headers to driver's root
>
> drivers/net/ntnic/meson.build | 3 +++
> .../nthw/flow_api/profile_inline/flow_api_profile_inline.c | 4 ++++
> .../nthw/flow_api/profile_inline/flow_api_profile_inline.h | 3 +++
> drivers/net/ntnic/{nthw => }/rte_pmd_ntnic.h | 0
> 4 files changed, 10 insertions(+)
> rename drivers/net/ntnic/{nthw => }/rte_pmd_ntnic.h (100%)
>
Applied to next-net
next prev parent reply other threads:[~2024-11-24 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 18:02 Serhii Iliushyk
2024-11-20 18:02 ` [PATCH v1 1/3] net/ntnic: fix action modify field DSCP Serhii Iliushyk
2024-11-20 18:02 ` [PATCH v1 2/3] net/ntnic: add supplementary macros Serhii Iliushyk
2024-11-20 18:02 ` [PATCH v1 3/3] net/ntnic: move headers to driver's root Serhii Iliushyk
2024-11-24 18:12 ` Stephen Hemminger [this message]
2024-11-25 10:27 ` [PATCH v1 0/3] Bugfixes Serhii Iliushyk
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=20241124101246.0b640966@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=ckm@napatech.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=mko-plv@napatech.com \
--cc=sil-plv@napatech.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).