From: Thomas Monjalon <thomas@monjalon.net>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
"Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH v2] doc: add deprecation notice for iavf devarg auto reconfig
Date: Wed, 22 Jul 2026 14:41:55 +0200 [thread overview]
Message-ID: <mlhkgerPRiWE9pm-OyoGXw@monjalon.net> (raw)
In-Reply-To: <16acd53d-6d66-44b5-acb0-feb495c96502@intel.com>
> > The `auto_reconfig` devarg in the iavf driver is enabled by default and the
> > case for ever disabling it is weak. When disabled, it means the user is
> > requesting the driver not to restore settings (unicast/multicast
> > promiscuous modes) when recovering from a reset. The use case where this
> > might be desired is during a VF initiated reset where the user initiates
> > the reset and wants the VF brought back up in an untouched state. That
> > scenario can be facilitated by extending the `rte_pmd_iavf_reinit` API
> > rather than relying on this devarg, so it should be safe to remove the
> > devarg.
> >
> > Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> > Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> Acked-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Acked-by: David Marchand <david.marchand@redhat.com>
Applied, thanks.
next prev parent reply other threads:[~2026-07-22 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 10:59 [PATCH] doc: add deprecation notice for iavf devarg auto reconfig Ciara Loftus
2026-07-15 12:01 ` Bruce Richardson
2026-07-15 12:20 ` [PATCH v2] " Ciara Loftus
2026-07-17 8:41 ` Medvedkin, Vladimir
2026-07-22 12:41 ` Thomas Monjalon [this message]
2026-07-17 8:46 ` David Marchand
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=mlhkgerPRiWE9pm-OyoGXw@monjalon.net \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=ciara.loftus@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=vladimir.medvedkin@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