patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: Re: [dpdk-stable] [PATCH 18.11] Revert "eal/freebsd: fix config creation"
Date: Fri, 31 Jan 2020 09:37:30 +0000	[thread overview]
Message-ID: <8a1afa58-11e7-091c-a2ad-86823253ce43@redhat.com> (raw)
In-Reply-To: <20200129134503.10897-1-ktraynor@redhat.com>

On 29/01/2020 13:45, Kevin Traynor wrote:
> This reverts commit 0d39a496a6be090f3f3288080c66cd04c566b185.
> 
> Reverted commit is a fix for dpdk master commit:
> b149a7064261 ("eal/freebsd: add config reattach in secondary process")
> which is not backported to DPDK 18.11 stable branch at this time.
> 
> Reverted commit can be re-applied if the fixed commit is
> backported to the stable branch.
> 
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> Cc: Anatoly Burakov <anatoly.burakov@intel.com>
> ---

Applied

>  lib/librte_eal/bsdapp/eal/eal.c | 5 -----
>  1 file changed, 5 deletions(-)
> 
> diff --git a/lib/librte_eal/bsdapp/eal/eal.c b/lib/librte_eal/bsdapp/eal/eal.c
> index e85c26ae64..30b4cf7bf0 100644
> --- a/lib/librte_eal/bsdapp/eal/eal.c
> +++ b/lib/librte_eal/bsdapp/eal/eal.c
> @@ -254,9 +254,4 @@ rte_eal_config_create(void)
>  	memcpy(rte_mem_cfg_addr, &early_mem_config, sizeof(early_mem_config));
>  	rte_config.mem_config = rte_mem_cfg_addr;
> -
> -	/* store address of the config in the config itself so that secondary
> -	 * processes could later map the config into this exact location
> -	 */
> -	rte_config.mem_config->mem_cfg_addr = (uintptr_t) rte_mem_cfg_addr;
>  }
>  
> 


      reply	other threads:[~2020-01-31  9:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 13:45 Kevin Traynor
2020-01-31  9:37 ` Kevin Traynor [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=8a1afa58-11e7-091c-a2ad-86823253ce43@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=stable@dpdk.org \
    /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).