From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples/flow_classify: fix fseek error handling
Date: Tue, 7 Nov 2017 00:22:16 -0800 [thread overview]
Message-ID: <b7d37adc-6f05-7c92-9a85-c6ec1ba9498b@intel.com> (raw)
In-Reply-To: <54CBAA185211B4429112C315DA58FF6D332802B7@IRSMSX103.ger.corp.intel.com>
On 11/3/2017 5:13 AM, Singh, Jasvinder wrote:
>
>
>> -----Original Message-----
>> From: Iremonger, Bernard
>> Sent: Wednesday, November 1, 2017 12:10 PM
>> To: dev@dpdk.org; Singh, Jasvinder <jasvinder.singh@intel.com>
>> Cc: Iremonger, Bernard <bernard.iremonger@intel.com>
>> Subject: [PATCH] examples/flow_classify: fix fseek error handling
>>
>> Check return value of fseek and exit if non zero.
>>
>> Coverity issue: 143435
>>
>> Fixes: bab16ddaf2c1 ("examples/flow_classify: add sample application")
>> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
> Acked-by: Jasvinder Singh <jasvinder.singh@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-11-07 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 12:10 Bernard Iremonger
2017-11-03 12:13 ` Singh, Jasvinder
2017-11-07 8:22 ` Ferruh Yigit [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=b7d37adc-6f05-7c92-9a85-c6ec1ba9498b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@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).