patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: David Marchand <david.marchand@redhat.com>, dev@dpdk.org
Cc: stable@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
	Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
	wathsala.vithanage@arm.com, nd@arm.com
Subject: Re: [PATCH] config: fix warning for cross build with meson >= 1.3.0
Date: Tue, 18 Jun 2024 09:18:32 +0800	[thread overview]
Message-ID: <dc79ecb1-f5ef-437a-8bc3-7c39dffe1ecd@arm.com> (raw)
In-Reply-To: <20240617151458.1005103-1-david.marchand@redhat.com>


On 2024/6/17 11:14 PM, David Marchand wrote:
> Starting meson 1.3.0, the pkgconfig variable is deprecated in favor of
> pkg-config. Keep both variables as suggested in meson RN.
> 
> Link: https://mesonbuild.com/Release-notes-for-1-3-0.html#machine-files-pkgconfig-field-deprecated-and-replaced-by-pkgconfig
> Cc: stable@dpdk.org
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
>   config/arm/arm32_armv8_linux_gcc          | 1 +
>   config/arm/arm64_altra_linux_gcc          | 1 +
>   config/arm/arm64_ampereone_linux_gcc      | 1 +
>   config/arm/arm64_armada_linux_gcc         | 1 +
>   config/arm/arm64_armv8_linux_clang_ubuntu | 1 +
>   config/arm/arm64_armv8_linux_gcc          | 1 +
>   config/arm/arm64_bluefield3_linux_gcc     | 1 +
>   config/arm/arm64_bluefield_linux_gcc      | 1 +
>   config/arm/arm64_capri_linux_gcc          | 1 +
>   config/arm/arm64_cdx_linux_gcc            | 1 +
>   config/arm/arm64_centriq2400_linux_gcc    | 1 +
>   config/arm/arm64_cn10k_linux_gcc          | 1 +
>   config/arm/arm64_cn9k_linux_gcc           | 1 +
>   config/arm/arm64_dpaa_linux_gcc           | 1 +
>   config/arm/arm64_elba_linux_gcc           | 1 +
>   config/arm/arm64_emag_linux_gcc           | 1 +
>   config/arm/arm64_ft2000plus_linux_gcc     | 1 +
>   config/arm/arm64_grace_linux_gcc          | 1 +
>   config/arm/arm64_graviton2_linux_gcc      | 1 +
>   config/arm/arm64_graviton3_linux_gcc      | 1 +
>   config/arm/arm64_graviton4_linux_gcc      | 1 +
>   config/arm/arm64_hip10_linux_gcc          | 1 +
>   config/arm/arm64_kunpeng920_linux_gcc     | 1 +
>   config/arm/arm64_kunpeng930_linux_gcc     | 1 +
>   config/arm/arm64_n1sdp_linux_gcc          | 1 +
>   config/arm/arm64_n2_linux_gcc             | 1 +
>   config/arm/arm64_odyssey_linux_gcc        | 1 +
>   config/arm/arm64_stingray_linux_gcc       | 1 +
>   config/arm/arm64_thunderx2_linux_gcc      | 1 +
>   config/arm/arm64_thunderxt83_linux_gcc    | 1 +
>   config/arm/arm64_thunderxt88_linux_gcc    | 1 +
>   config/arm/arm64_tys2500_linux_gcc        | 1 +
>   config/arm/arm64_v2_linux_gcc             | 1 +
>   config/x86/cross-mingw                    | 1 +
>   34 files changed, 34 insertions(+)
> 

Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>

      parent reply	other threads:[~2024-06-18  1:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17 15:14 David Marchand
2024-06-17 15:19 ` Bruce Richardson
2024-06-25 12:36   ` David Marchand
2024-06-18  1:18 ` Ruifeng Wang [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=dc79ecb1-f5ef-437a-8bc3-7c39dffe1ecd@arm.com \
    --to=ruifeng.wang@arm.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=nd@arm.com \
    --cc=stable@dpdk.org \
    --cc=wathsala.vithanage@arm.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).