patches for DPDK stable branches
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Timothy Redaelli <tredaelli@redhat.com>
Cc: stable@dpdk.org, Andrew Boyer <andrew.boyer@amd.com>,
	Luca Boccassi <bluca@debian.org>,
	Kevin Traynor <ktraynor@redhat.com>
Subject: Re: [PATCH 23.11] net/ionic: fix build with Fedora Rawhide
Date: Thu, 24 Oct 2024 12:12:33 +0200	[thread overview]
Message-ID: <CAJFAV8wjd28LoNczxdGfUHK3=7BNOB80y6u1PtCfVJXu0ZF0CA@mail.gmail.com> (raw)
In-Reply-To: <b0d2381ba889e22ee0f695e2a27043c6ab5c068d.1729760024.git.tredaelli@redhat.com>

On Thu, Oct 24, 2024 at 11:30 AM Timothy Redaelli <tredaelli@redhat.com> wrote:
>
> Currently, a number of integer types are typedef'd to their corresponding
> userspace or RTE values. This can be problematic if these types are
> already defined somewhere else, as it would cause type collisions.
> This patch changes the typedefs to #define macros which are only defined
> if the types are not defined already.
>
> Fixes: 5ef518098ec6 ("net/ionic: register and initialize adapter")
>
> Signed-off-by: Timothy Redaelli <tredaelli@redhat.com>

Copying driver maintainer.
The patch lgtm on the principle.


> ---
> Backport of f0d9e787747d ("net/gve/base: fix build with Fedora Rawhide")
> is also needed on stable branches. My commit is not needed on
> main since it was fixed silently in 484027bf9452 ("common/ionic: create common
> code library").
> ---

Indeed, it is a pity this got mixed in the mentionned commit.

This may be needed in others LTS.
Copying Luca and Kevin.


-- 
David Marchand


  reply	other threads:[~2024-10-24 10:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24  9:30 Timothy Redaelli
2024-10-24 10:12 ` David Marchand [this message]
2024-10-27  8:05   ` Xueming Li

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='CAJFAV8wjd28LoNczxdGfUHK3=7BNOB80y6u1PtCfVJXu0ZF0CA@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=andrew.boyer@amd.com \
    --cc=bluca@debian.org \
    --cc=ktraynor@redhat.com \
    --cc=stable@dpdk.org \
    --cc=tredaelli@redhat.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).