From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Trybula, ArturX" <arturx.trybula@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"Trybula, ArturX" <arturx.trybula@intel.com>,
"Dybkowski, AdamX" <adamx.dybkowski@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/test-compress-perf: fix reliance on integer endianness (CI:328524)
Date: Tue, 4 Jun 2019 09:05:08 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE24BBF49BA@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <20190603135046.26572-1-arturx.trybula@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Artur Trybula
> Sent: Monday, June 3, 2019 2:51 PM
> To: dev@dpdk.org; Trahe, Fiona <fiona.trahe@intel.com>; Trybula, ArturX
> <arturx.trybula@intel.com>; Dybkowski, AdamX <adamx.dybkowski@intel.com>
> Subject: [dpdk-dev] [PATCH] app/test-compress-perf: fix reliance on
> integer endianness (CI:328524)
>
> This patch fixes Coverity Issue 328524:
> Reliance on integer endianness (INCOMPATIBLE_CAST) in function
> *parse_window_sz*.
This patch should have a fixes line. The usual message would include:
Fixes: e0b6287c035d ("app/compress-perf: add parser")
Coverity issue: 328524
John
next prev parent reply other threads:[~2019-06-04 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 13:50 Artur Trybula
2019-06-04 9:05 ` Mcnamara, John [this message]
2019-06-04 12:41 ` [dpdk-dev] [PATCH v2 0/1] app/test-compress-perf: fix reliance on integer endianness Artur Trybula
2019-06-04 12:41 ` [dpdk-dev] [PATCH v2 1/1] " Artur Trybula
2019-06-26 17:06 ` Shally Verma
2019-07-01 11:37 ` Akhil Goyal
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=B27915DBBA3421428155699D51E4CFE24BBF49BA@IRSMSX104.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=adamx.dybkowski@intel.com \
--cc=arturx.trybula@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).