DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jianfeng Tan <jianfeng.tan@intel.com>
Cc: dev@dpdk.org, harry.van.haaren@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: fix wrong config file path
Date: Wed, 05 Jul 2017 15:07:01 +0200	[thread overview]
Message-ID: <3010055.C34feptO8o@xps> (raw)
In-Reply-To: <1498459786-4523-1-git-send-email-jianfeng.tan@intel.com>

26/06/2017 08:49, Jianfeng Tan:
> When primary process is booted with --file-prefix option, the API,
> rte_eal_primary_proc_alive(), uses a wrong config file path to
> check if primary process is alive.
> 
> Fix it by calling helper function to get config file path.
> 
> Fixes: dd3e00138d74 ("eal: check if primary process is alive")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>

Applied, thanks

      reply	other threads:[~2017-07-05 13:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26  6:49 Jianfeng Tan
2017-07-05 13:07 ` Thomas Monjalon [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=3010055.C34feptO8o@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@intel.com \
    --cc=jianfeng.tan@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).