On 4/23/2018 1:16 PM, Xueming Li wrote: > Remove deprecation as implementation of RSS level provided in Adrien's > patch set: http://www.dpdk.org/dev/patchwork/patch/37399/
Why deprecation notice removed in this set if the implementation is in other set, or am I missing something? > > Signed-off-by: Xueming Li <xuemi...@mellanox.com> > Acked-by: Adrien Mazarguil <adrien.mazarg...@6wind.com> > Acked-by: Thomas Monjalon <tho...@monjalon.net> > --- > doc/guides/rel_notes/deprecation.rst | 4 ---- > 1 file changed, 4 deletions(-) > > diff --git a/doc/guides/rel_notes/deprecation.rst > b/doc/guides/rel_notes/deprecation.rst > index 93747bf24..aba50b8ec 100644 > --- a/doc/guides/rel_notes/deprecation.rst > +++ b/doc/guides/rel_notes/deprecation.rst > @@ -86,10 +86,6 @@ Deprecation Notices > Target release for removal of the legacy API will be defined once most > PMDs have switched to rte_flow. > > -* ethdev: A new rss level field planned in 18.05. > - The new API add rss_level field to ``rte_eth_rss_conf`` to enable a choice > - of RSS hash calculation on outer or inner header of tunneled packet. > - > * ethdev: A work is being planned for 18.05 to expose VF port representors > as a mean to perform control and data path operation on the different VFs. > As VF representor is an ethdev port, new fields are needed in order to map >
