From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v1 1/1] net/iavf: fix order of inclusion in vector code
Date: Wed, 09 Jul 2025 15:46:03 +0200 [thread overview]
Message-ID: <23891910.mFnZMskM5D@thomas> (raw)
In-Reply-To: <aG5ueFRWP86CUrZa@bricha3-mobl1.ger.corp.intel.com>
09/07/2025 15:28, Bruce Richardson:
> On Wed, Jul 09, 2025 at 02:06:29PM +0100, Anatoly Burakov wrote:
> > IAVF driver does not support 16-byte descriptors (because there is no PF
> > that can support a VF using 16-byte descriptor), but if IAVF is built with
> > a flag that enables 16-byte descriptors, this flag is then propagated
> > through the inclusion chain in certain cases, because IAVF includes common
> > vector code before IAVF-specific common code (which in turn includes
> > `iavf_rxtx.h` which disables 16-byte descriptor support).
> >
> > Fix the inclusion order to include IAVF-specific vector header first, which
> > will fix the compilation error due to correctly disabling 16-byte Rx
> > descriptor support.
> >
> > Bugzilla ID: 1749
> >
> > Fixes: 11276ec5e042 ("net/iavf: use common Rx rearm")
> >
> > Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> > ---
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, thanks.
prev parent reply other threads:[~2025-07-09 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 13:06 [PATCH v1 1/1] net/iavf: fix order of inclusion in vector code Anatoly Burakov
2025-07-09 13:28 ` Bruce Richardson
2025-07-09 13:46 ` Thomas Monjalon [this message]
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=23891910.mFnZMskM5D@thomas \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.