From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>, david.hunt@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] power: update for error handling
Date: Thu, 28 Mar 2019 17:02:32 +0000 [thread overview]
Message-ID: <b6976f46-773b-8e56-ec1c-d33736e623f2@intel.com> (raw)
In-Reply-To: <20190328155507.3608-1-lukaszx.krakowiak@intel.com>
On 28-Mar-19 3:55 PM, Lukasz Krakowiak wrote:
> Update for handling negative returned status from functions
> call.
>
> Signed-off-by: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-03-28 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 15:55 Lukasz Krakowiak
2019-03-28 15:55 ` Lukasz Krakowiak
2019-03-28 17:02 ` Burakov, Anatoly [this message]
2019-03-28 17:02 ` Burakov, Anatoly
2019-03-29 14:32 ` Thomas Monjalon
2019-03-29 14:32 ` 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=b6976f46-773b-8e56-ec1c-d33736e623f2@intel.com \
--to=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=lukaszx.krakowiak@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).