From: Shahaf Shuler <shahafs@mellanox.com>
To: Yongseok Koh <yskoh@mellanox.com>, Ori Kam <orika@mellanox.com>
Cc: dev <dev@dpdk.org>, Dekel Peled <dekelp@mellanox.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix modify header action position
Date: Thu, 18 Apr 2019 18:55:11 +0000 [thread overview]
Message-ID: <AM6PR0502MB37977AD080227708C8328380C3260@AM6PR0502MB3797.eurprd05.prod.outlook.com> (raw)
Message-ID: <20190418185511.fXqQ2aM8IYqLRujM8T3xKlMk0rp_uGMbNzjtRQdpQFA@z> (raw)
In-Reply-To: <A04C7AFB-6FC7-425A-AFEC-3F7D1DA2D2AC@mellanox.com>
Thursday, April 18, 2019 4:26 PM, Yongseok Koh:
> Subject: Re: [PATCH v2] net/mlx5: fix modify header action position
>
>
> > On Apr 17, 2019, at 1:01 PM, Ori Kam <orika@mellanox.com> wrote:
> >
> > According to RTE flow the action order should be the order that the
> > actions were given.
> > In the case of modify actions the position of the action was always
> > last.
> >
> > This commit solves this issue by saving the position of the first
> > modify action, and then adds to this position the pointer to the modify
> action.
> >
> > Fixes: 4bb14c83df95 ("net/mlx5: support modify header using Direct
> > Verbs")
> > Cc: dekelp@mellanox.com
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Ori Kam <orika@mellanox.com>
> > ---
> Acked-by: Yongseok Koh <yskoh@mellanox.com>
Applied to next-net-mlx, thanks.
next prev parent reply other threads:[~2019-04-18 18:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 20:19 [dpdk-dev] [PATCH] " Ori Kam
2019-04-14 20:19 ` Ori Kam
2019-04-16 23:41 ` Yongseok Koh
2019-04-16 23:41 ` Yongseok Koh
2019-04-17 5:03 ` Ori Kam
2019-04-17 5:03 ` Ori Kam
2019-04-17 20:01 ` [dpdk-dev] [PATCH v2] " Ori Kam
2019-04-17 20:01 ` Ori Kam
2019-04-18 13:25 ` Yongseok Koh
2019-04-18 13:25 ` Yongseok Koh
2019-04-18 18:55 ` Shahaf Shuler [this message]
2019-04-18 18:55 ` Shahaf Shuler
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=AM6PR0502MB37977AD080227708C8328380C3260@AM6PR0502MB3797.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=orika@mellanox.com \
--cc=stable@dpdk.org \
--cc=yskoh@mellanox.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).