From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Qiming Yang <qiming.yang@intel.com>,
Wenjun Wu <wenjun1.wu@intel.com>,
Jiawen Wu <jiawenwu@trustnetic.com>,
Jian Wang <jianwang@trustnetic.com>,
Yuying Zhang <Yuying.Zhang@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Rasesh Mody <rmody@marvell.com>,
Devendra Singh Rawat <dsinghrawat@marvell.com>
Cc: <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH 0/3] ethdev: remove deprecated Flow Director configuration
Date: Wed, 24 Aug 2022 10:42:45 +0100 [thread overview]
Message-ID: <153881f1-70c7-0c63-3f40-280f6c867403@xilinx.com> (raw)
In-Reply-To: <20220803111358.375544-1-andrew.rybchenko@oktetlabs.ru>
On 8/3/2022 12:13 PM, Andrew Rybchenko wrote:
> Flow Director configuration fdir_conf was deprecated long time ago and
> was planned to be removed in 20.11.
>
> i40e, ixgbe, qede and txgbe driver maintainers are encouraged to review
> correspodning patches very carefully.
>
> Internal copy of the Flow Director configuration in ixgbe and txgbe
> drivers is not actually initialized. Should I use configuration from
> testpmd as the default one?
>
> Andrew Rybchenko (3):
> net/ixgbe: add helper to get Flow Director configuration
> net/txgbe: add helper to get Flow Director configuration
> ethdev: remove deprecated Flow Director configuration
>
Thanks Andrew, this is one of the long lasting deprecating notices.
Change looks good to me, but impacted driver (ixgbe, txgbe, i40e, qede)
maintainers, can you please looks at the change, if there is no comment
it will proceed.
next prev parent reply other threads:[~2022-08-24 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 11:13 Andrew Rybchenko
2022-08-03 11:13 ` [PATCH 1/3] net/ixgbe: add helper to get " Andrew Rybchenko
2022-08-03 11:13 ` [PATCH 2/3] net/txgbe: " Andrew Rybchenko
2022-08-03 11:13 ` [PATCH 3/3] ethdev: remove deprecated " Andrew Rybchenko
2022-08-04 11:07 ` Dongdong Liu
2022-08-24 9:42 ` Ferruh Yigit [this message]
2022-08-31 13:27 ` [PATCH 0/3] " 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=153881f1-70c7-0c63-3f40-280f6c867403@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=Yuying.Zhang@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=dsinghrawat@marvell.com \
--cc=jianwang@trustnetic.com \
--cc=jiawenwu@trustnetic.com \
--cc=qiming.yang@intel.com \
--cc=rmody@marvell.com \
--cc=thomas@monjalon.net \
--cc=wenjun1.wu@intel.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).