DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: bluca@debian.org, tredaelli@redhat.com,
	Marco Varlese <mvarlese@suse.de>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add deprecation notice for meson version
Date: Wed, 16 Jan 2019 14:41:08 +0000	[thread overview]
Message-ID: <20190116144108.GA152812@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20190116113713.40009-1-bruce.richardson@intel.com>

+ Marco and Christian to ensure I get the most distro awareness.

On Wed, Jan 16, 2019 at 11:37:13AM +0000, Bruce Richardson wrote:
> Add a notice in the deprecation section of the release notes to call out
> the fact that the minimum supported meson version for DPDK will change
> from 19.05 onwards.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index d4aea4b46..92524e4e3 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -17,6 +17,12 @@ Deprecation Notices
>    Long Term Stable (LTS) version which is 3.16, but compatibility for
>    recent distribution kernels will be kept.
>  
> +* meson: The minimum supported version of meson for configuring and building
> +  DPDK will be increased to v0.47.1 (from 0.41) from DPDK 19.05 onwards. For
> +  those users with a version earlier than 0.47.1, an updated copy of meson
> +  can be got using the ``pip``, or ``pip3``, tool for downloading python
> +  packages.
> +
>  * kvargs: The function ``rte_kvargs_process`` will get a new parameter
>    for returning key match count. It will ease handling of no-match case.
>  
> -- 
> 2.20.1
> 

  parent reply	other threads:[~2019-01-16 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 11:37 Bruce Richardson
2019-01-16 11:42 ` Luca Boccassi
2019-01-16 13:44 ` Timothy Redaelli
2019-01-16 14:41 ` Bruce Richardson [this message]
2019-01-16 14:56   ` Luca Boccassi
2019-01-25 17:45 ` Van Haaren, Harry
2019-02-01 11:10 ` Thomas Monjalon

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=20190116144108.GA152812@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=mvarlese@suse.de \
    --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).