patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Xueming Li <xuemingl@nvidia.com>
To: David Marchand <david.marchand@redhat.com>,
	Timothy Redaelli <tredaelli@redhat.com>
Cc: "stable@dpdk.org" <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: Sun, 27 Oct 2024 08:05:25 +0000	[thread overview]
Message-ID: <CH3PR12MB8658B1E32998D2786F91FAFCA1492@CH3PR12MB8658.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8wjd28LoNczxdGfUHK3=7BNOB80y6u1PtCfVJXu0ZF0CA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]

Hi Timothy,

Thanks for taking care of this, patch applied to 23.11.3 LTS queue.

Regards,
Xueming
________________________________
From: David Marchand <david.marchand@redhat.com>
Sent: Thursday, October 24, 2024 6:12 PM
To: Timothy Redaelli <tredaelli@redhat.com>
Cc: stable@dpdk.org <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

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


[-- Attachment #2: Type: text/html, Size: 3439 bytes --]

      reply	other threads:[~2024-10-27  8:05 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
2024-10-27  8:05   ` Xueming Li [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=CH3PR12MB8658B1E32998D2786F91FAFCA1492@CH3PR12MB8658.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=andrew.boyer@amd.com \
    --cc=bluca@debian.org \
    --cc=david.marchand@redhat.com \
    --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).