DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, techboard@dpdk.org, david.marchand@redhat.com,
	Ray Kinsella <mdr@ashroe.eu>, Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [dpdk-dev] [PATCH v2] eal: simplify exit functions
Date: Mon, 28 Sep 2020 09:41:01 +0100	[thread overview]
Message-ID: <20200928084101.GA951@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20200928000049.3245920-1-thomas@monjalon.net>

On Mon, Sep 28, 2020 at 02:00:48AM +0200, Thomas Monjalon wrote:
> The option RTE_EAL_ALWAYS_PANIC_ON_ERROR was off by default,
> and not customizable with meson. It is completely removed.
> 
> The function rte_dump_registers is a trace of the bare metal support
> era, and was not supported in userland. It is completely removed.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> Acked-by: Ray Kinsella <mdr@ashroe.eu>
> ---
> The deprecation notice for this removal has been missed.
> I assume it would not hurt anybody to remove this useless function
> from DPDK 20.11. Asking the Technical Board for confirmation.
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>


  reply	other threads:[~2020-09-28  8:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24  9:36 [dpdk-dev] [PATCH 20.11] " Thomas Monjalon
2020-06-30 10:26 ` Kinsella, Ray
2020-09-28  0:00 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2020-09-28  8:41   ` Bruce Richardson [this message]
2020-09-28 11:21   ` [dpdk-dev] [dpdk-techboard] " Ananyev, Konstantin
2020-09-30  9:01   ` Kevin Traynor
2020-10-08  7:51   ` [dpdk-dev] " David Marchand
2020-10-12 17:39   ` David Marchand
2020-10-15 20:38     ` David Marchand

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=20200928084101.GA951@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mdr@ashroe.eu \
    --cc=nhorman@tuxdriver.com \
    --cc=techboard@dpdk.org \
    --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).