DPDK patches and discussions
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: Bruce Richardson <bruce.richardson@intel.com>, <dev@dpdk.org>
Cc: <mb@smartsharesystems.com>, <thomas@monjalon.net>,
	<david.marchand@redhat.com>
Subject: Re: [PATCH 0/5] Increase minimum meson version
Date: Mon, 23 Sep 2024 09:59:35 +0800	[thread overview]
Message-ID: <3d1919bc-36d7-4494-af96-a0953763eb34@huawei.com> (raw)
In-Reply-To: <20240920125737.1197969-1-bruce.richardson@intel.com>

Acked-by: Chengwen Feng <fengchengwen@huawei.com>

On 2024/9/20 20:57, Bruce Richardson wrote:
> This patchset proposed increasing the minimum meson version to 0.57
> and makes changes to update our build files appropriately for that
> change: replacing deprecated functions, removing unnecessary version
> checks and taking advantage of some new capabilities.
> 
> Why 0.57? No one particular reason; it's mainly a conservative version
> bump that doesn't have many impacts, but still gives us the minimum
> updates we need to replace the deprecated get_cross_properties fn
> and have a few extra features guaranteed available.
> 
> Bruce Richardson (5):
>   build: increase minimum meson version to 0.57
>   build: remove version check on compiler links function
>   build: remove unnecessary version checks
>   build: use version file support from meson
>   build: replace deprecated meson function
> 
>  .ci/linux-setup.sh                        | 2 +-
>  config/arm/meson.build                    | 4 ++--
>  config/meson.build                        | 8 ++++----
>  config/riscv/meson.build                  | 4 ++--
>  doc/api/meson.build                       | 2 +-
>  doc/guides/linux_gsg/sys_reqs.rst         | 2 +-
>  doc/guides/prog_guide/build-sdk-meson.rst | 2 +-
>  drivers/common/qat/meson.build            | 2 +-
>  drivers/crypto/ipsec_mb/meson.build       | 2 +-
>  drivers/event/cnxk/meson.build            | 2 +-
>  drivers/meson.build                       | 7 ++-----
>  drivers/net/cnxk/meson.build              | 2 +-
>  lib/meson.build                           | 6 ------
>  meson.build                               | 7 ++-----
>  14 files changed, 20 insertions(+), 32 deletions(-)
> 
> --
> 2.43.0
> 


  parent reply	other threads:[~2024-09-23  1:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20 12:57 Bruce Richardson
2024-09-20 12:57 ` [PATCH 1/5] build: increase minimum meson version to 0.57 Bruce Richardson
2024-09-20 12:57 ` [PATCH 2/5] build: remove version check on compiler links function Bruce Richardson
2024-09-20 12:57 ` [PATCH 3/5] build: remove unnecessary version checks Bruce Richardson
2024-09-20 12:57 ` [PATCH 4/5] build: use version file support from meson Bruce Richardson
2024-09-20 12:57 ` [PATCH 5/5] build: replace deprecated meson function Bruce Richardson
2024-09-21 23:21 ` [PATCH 0/5] Increase minimum meson version Ferruh Yigit
2024-09-23  1:59 ` fengchengwen [this message]
2024-09-23  2:19   ` fengchengwen

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=3d1919bc-36d7-4494-af96-a0953763eb34@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=thomas@monjalon.net \
    /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).