DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, dev@dpdk.org
Cc: rasland@nvidia.com
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix 32-bit arch compilation issue
Date: Thu, 28 Jan 2021 18:22:47 +0000	[thread overview]
Message-ID: <e4a952b7-f684-4288-fa54-f1549e8d3653@intel.com> (raw)
In-Reply-To: <20210128171030.17013-1-akozyrev@nvidia.com>

On 1/28/2021 5:10 PM, Alexander Kozyrev wrote:
> There is a "cast to pointer from integer of different size"
> compilation failure on 32-bit machines introduced by the
> RTE_FLOW_ACTION_TYPE_MODIFY_FIELD implementation in mlx5 PMD.
> 
> Cast the specified value to be used as RTE_FLOW_FIELD_POINTER
> to a pointer with an appropriate size suited for underlying arch.
> Please squash this patch into the original commit if possible.
> 
> Fixes: 80ec1e84a4 ("net/mlx5: support modify field flow action")
> 
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>

Squashed into relevant commit in next-net, thanks.

      reply	other threads:[~2021-01-28 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 17:10 Alexander Kozyrev
2021-01-28 18:22 ` Ferruh Yigit [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=e4a952b7-f684-4288-fa54-f1549e8d3653@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=akozyrev@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=rasland@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).