DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: David Christensen <drc@linux.ibm.com>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>,
	 Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
	 Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>,
	dev@dpdk.org, Ali Alnubani <alialnu@nvidia.com>
Subject: Re: [PATCH] drivers/net: fix cast-qual and strict-aliasing errors for ppc64le
Date: Thu, 30 Jan 2025 09:15:45 +0100	[thread overview]
Message-ID: <CAJFAV8ybU0wB69wVvj7NgbGHEgQ8NXBCmc4+TvEwrkj+angGhQ@mail.gmail.com> (raw)
In-Reply-To: <1738172139-31201-1-git-send-email-andremue@linux.microsoft.com>

On Wed, Jan 29, 2025 at 6:36 PM Andre Muezerie
<andremue@linux.microsoft.com> wrote:
>
> During a recent cleanup a few lines were missed which are causing
> errors on ppc64le, like the ones below:
>
> drivers/net/mlx5/mlx5_rxtx_vec_altivec.h:77:17: error: cast discards
> ‘volatile’ qualifier from pointer target type [-Werror=cast-qual]
>
> lib/eal/include/rte_common.h:557:34: warning: dereferencing type-punned
> pointer will break strict-aliasing rules [-Wstrict-aliasing]
>
Fixes: 43fd3624fdfe ("drivers: replace GCC pragma with cast")

> Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
Reviewed-by: David Marchand <david.marchand@redhat.com>
> Tested-by: Ali Alnubani <alialnu@nvidia.com>

Applied, thanks.


-- 
David Marchand


      parent reply	other threads:[~2025-01-30  8:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 17:35 Andre Muezerie
2025-01-30  8:02 ` David Marchand
2025-01-30  8:07   ` Ali Alnubani
2025-01-30  8:15 ` David Marchand [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=CAJFAV8ybU0wB69wVvj7NgbGHEgQ8NXBCmc4+TvEwrkj+angGhQ@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=andremue@linux.microsoft.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.ibm.com \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --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).