From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org
Cc: rasland@nvidia.com, getelson@nvidia.com, viacheslavo@nvidia.com
Subject: Re: [PATCH 21.11] Revert "net/mlx5: fix flex item availability"
Date: Fri, 1 Apr 2022 11:23:42 +0100 [thread overview]
Message-ID: <0e1f23ff-fca0-4b9b-76a8-b89181c47987@redhat.com> (raw)
In-Reply-To: <20220329154116.151735-1-ktraynor@redhat.com>
On 29/03/2022 16:41, Kevin Traynor wrote:
> This reverts commit 48fe9efaf2fb974e3f805eb7c54440ec3818a4b6.
>
> This patch seems to be causing a build failure [0] in the CI [1] with
> meson on Windows.
>
> Revert for now and it can be reapplied at a later time when it is fixed.
>
> [0]
> [531/617] Compiling C object
> drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow.c.obj.
> FAILED: drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow.c.obj
> clang @drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow.c.obj.rsp
> ../drivers/net/mlx5/mlx5_flow.c:9867:23: error: incomplete definition of
> type 'struct rte_pci_device'
> switch (priv->pci_dev->id.device_id) {
> ~~~~~~~~~~~~~^
> ..\drivers\net/mlx5/mlx5.h:154:9: note: forward declaration of 'struct
> rte_pci_device'
> struct rte_pci_device *pci_dev; /**< Backend PCI device. */
> ^
> 1 error generated.
>
> [1]
> https://lab.dpdk.org/results/dashboard/tarballs/19198/#env-27
>
> Cc: rasland@nvidia.com
> Cc: getelson@nvidia.com
> Cc: viacheslavo@nvidia.com
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
Applied.
prev parent reply other threads:[~2022-04-01 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 15:41 Kevin Traynor
2022-04-01 10:23 ` Kevin Traynor [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=0e1f23ff-fca0-4b9b-76a8-b89181c47987@redhat.com \
--to=ktraynor@redhat.com \
--cc=getelson@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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).