On Tue, Mar 09, 2021 at 09:11:46PM -0800, Jesse Brandeburg wrote:
> Leon Romanovsky wrote:
>
> > > 3) Plan is to make the "new" iavf driver the default iavf once
> > >extensive regression testing can be completed.
> > > a. Current proposal is to make CONFIG_IAVF have a sub-option
> > > C
Jakub Kicinski wrote:
> On Mon, 8 Mar 2021 16:28:58 -0800 Jesse Brandeburg wrote:
> > Hello,
> >
> > We plan to refactor the iavf module and would appreciate community and
> > maintainer feedback on our plans. We want to do this to realize the
> > usefulness of the common code module for multipl
Leon Romanovsky wrote:
> > 3) Plan is to make the "new" iavf driver the default iavf once
> >extensive regression testing can be completed.
> > a. Current proposal is to make CONFIG_IAVF have a sub-option
> >CONFIG_IAVF_V2 that lets the user adopt the new code,
> >without c
On Mon, 8 Mar 2021 16:28:58 -0800 Jesse Brandeburg wrote:
> Hello,
>
> We plan to refactor the iavf module and would appreciate community and
> maintainer feedback on our plans. We want to do this to realize the
> usefulness of the common code module for multiple drivers. This
> proposal aims to
On Mon, Mar 08, 2021 at 04:28:58PM -0800, Jesse Brandeburg wrote:
> Hello,
>
> We plan to refactor the iavf module and would appreciate community and
> maintainer feedback on our plans. We want to do this to realize the
> usefulness of the common code module for multiple drivers. This
> proposal
Hello,
We plan to refactor the iavf module and would appreciate community and
maintainer feedback on our plans. We want to do this to realize the
usefulness of the common code module for multiple drivers. This
proposal aims to avoid disrupting current users.
The steps we plan are something like
