DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: <dev@dpdk.org>, Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: Re: [PATCH v1 1/1] net/iavf: fix order of inclusion in vector code
Date: Wed, 9 Jul 2025 14:28:24 +0100	[thread overview]
Message-ID: <aG5ueFRWP86CUrZa@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <552f8241f4f65fce0c8b43797612a97dec5d9ebc.1752066381.git.anatoly.burakov@intel.com>

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>

  reply	other threads:[~2025-07-09 13:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 13:06 Anatoly Burakov
2025-07-09 13:28 ` Bruce Richardson [this message]
2025-07-09 13:46   ` Thomas Monjalon

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=aG5ueFRWP86CUrZa@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@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 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).