From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Ye, Xiaolong" <xiaolong.ye@intel.com>,
"Zhang, Tianfei" <tianfei.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Xu, Rosen" <rosen.xu@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Zhang@dpdk.org" <Zhang@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v1 2/2] raw/ifpga: fix logically dead code
Date: Tue, 4 Jun 2019 09:06:15 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE24BBF49F7@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <20190604072646.GB94383@intel.com>
> -----Original Message-----
> From: stable [mailto:stable-bounces@dpdk.org] On Behalf Of Ye Xiaolong
> Sent: Tuesday, June 4, 2019 8:27 AM
> To: Zhang, Tianfei <tianfei.zhang@intel.com>
> Cc: dev@dpdk.org; Xu, Rosen <rosen.xu@intel.com>; stable@dpdk.org;
> Zhang@dpdk.org
> Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v1 2/2] raw/ifpga: fix
> logically dead code
>
> On 06/04, Zhang, Tianfei wrote:
> >add temporary variable in max10_reg_write().
> >
> >Coverity issue: 337927
> >Cc: stable@dpdk.org
>
> Missing a Fixes line?
>
In this case it would be:
Fixes: 96ebfcf8125c ("raw/ifpga/base: add SPI and MAX10 device driver")
Coverity issue: 337927
John
prev parent reply other threads:[~2019-06-04 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 13:51 [dpdk-dev] [PATCH v1 1/2] raw/ifpga: fix use of untrusted scalar value Zhang, Tianfei
2019-06-04 7:29 ` Ye Xiaolong
2019-06-04 8:03 ` Zhang, Tianfei
2019-06-04 13:51 ` [dpdk-dev] [PATCH v1 2/2] raw/ifpga: fix logically dead code Zhang, Tianfei
2019-06-04 7:26 ` Ye Xiaolong
2019-06-04 9:06 ` Mcnamara, John [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=B27915DBBA3421428155699D51E4CFE24BBF49F7@IRSMSX104.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=Zhang@dpdk.org \
--cc=dev@dpdk.org \
--cc=rosen.xu@intel.com \
--cc=stable@dpdk.org \
--cc=tianfei.zhang@intel.com \
--cc=xiaolong.ye@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).