From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>, dev@dpdk.org
Cc: Ivan Malov <ivan.malov@oktetlabs.ru>
Subject: Re: [dpdk-dev] [PATCH] common/sfc_efx/base: fix prefix in struct member names
Date: Fri, 30 Oct 2020 14:20:05 +0000 [thread overview]
Message-ID: <def68bd8-6882-ba9b-30b8-d70d9aa7d30e@intel.com> (raw)
In-Reply-To: <1603957185-29309-1-git-send-email-arybchenko@solarflare.com>
On 10/29/2020 7:39 AM, Andrew Rybchenko wrote:
> From: Ivan Malov <ivan.malov@oktetlabs.ru>
>
> In libefx, a struct member name prefix is an abbreviation for the
> struct name. Fix mismatch in the case of action set spec struct.
>
> Fixes: aeacb8458950 ("common/sfc_efx/base: support adding DELIVER action to set")
> Fixes: c73d314f790c ("common/sfc_efx/base: support adding VLAN POP action to set")
> Fixes: 19aa67196d08 ("common/sfc_efx/base: support adding VLAN PUSH action")
> Fixes: 633a89842c17 ("common/sfc_efx/base: support adding MARK action to set")
>
> Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
> Reviewed-by: Andy Moreton <amoreton@xilinx.com>
Squashed into relevant commit in next-net, thanks.
Please confirm it from latest head of next-net.
Unfortunately this will cause conflicts to the vendor sub-trees.
next prev parent reply other threads:[~2020-10-30 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 7:39 Andrew Rybchenko
2020-10-30 14:20 ` Ferruh Yigit [this message]
2020-11-02 9:22 ` Ivan Malov
2020-11-02 10:45 ` Ferruh Yigit
2020-11-02 11:18 ` Ferruh Yigit
2020-11-02 12:03 ` Ivan Malov
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=def68bd8-6882-ba9b-30b8-d70d9aa7d30e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ivan.malov@oktetlabs.ru \
/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).