DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Jianfeng Tan <jianfeng.tan@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mem: fix handling return value
Date: Thu, 26 Apr 2018 09:10:51 +0100	[thread overview]
Message-ID: <05d4ca37-6464-dd2b-de53-27c767ccbc27@intel.com> (raw)
In-Reply-To: <1524730013-61990-1-git-send-email-jianfeng.tan@intel.com>

On 26-Apr-18 9:06 AM, Jianfeng Tan wrote:
> resize_hugefile() returns either 0 (which indicates success) or -1
> (which indicates failure). We failed to check the success as we
> use --single-file-segments option.
> 
> Fixes: 2a04139f66b4 ("eal: add single file segments option")
> 
> Cc: Anatoly Burakov <anatoly.burakov@intel.com>
> 
> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
> ---

Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>

-- 
Thanks,
Anatoly

  reply	other threads:[~2018-04-26  8:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26  8:06 Jianfeng Tan
2018-04-26  8:10 ` Burakov, Anatoly [this message]
2018-04-27 21:38   ` 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=05d4ca37-6464-dd2b-de53-27c767ccbc27@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.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).