DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gao, DaxueX" <daxuex.gao@intel.com>
To: Rakesh Kudurumalla <rkudurumalla@marvell.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	"Sunil Kumar Kori" <skori@marvell.com>,
	Satha Rao <skoteshwar@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	 "stable@dpdk.org" <stable@dpdk.org>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: RE: [PATCH] net/cnxk: fix error when compiled for x86
Date: Mon, 7 Mar 2022 06:51:45 +0000	[thread overview]
Message-ID: <CO1PR11MB5011E6BB28B9EC93090363059D089@CO1PR11MB5011.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220304142337.911828-1-rkudurumalla@marvell.com>

> -----Original Message-----
> From: Rakesh Kudurumalla <rkudurumalla@marvell.com>
> Sent: 2022年3月4日 22:24
> To: Nithin Dabilpuram <ndabilpuram@marvell.com>; Kiran Kumar K
> <kirankumark@marvell.com>; Sunil Kumar Kori <skori@marvell.com>; Satha
> Rao <skoteshwar@marvell.com>
> Cc: dev@dpdk.org; jerinj@marvell.com; Rakesh Kudurumalla
> <rkudurumalla@marvell.com>; stable@dpdk.org; Yigit, Ferruh
> <ferruh.yigit@intel.com>
> Subject: [PATCH] net/cnxk: fix error when compiled for x86
> 
> fix error when compiled for x86 platform when compiled with optimization flag
> enabled
> error: ‘str’ may be used uninitialized in this function
> error: ‘frag_ptr’ may be used uninitialized in this function
> 
> Bugzilla ID: 939
> Fixes: b526599020ef ("net/cnxk: fix build with GCC 12")
> Cc: stable@dpdk.org
> 
> Reported-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Signed-off-by: Rakesh Kudurumalla <rkudurumalla@marvell.com>
> ---

Tested-by: Daxue Gao <daxuex.gao@intel.com>

  reply	other threads:[~2022-03-07  6:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 14:23 Rakesh Kudurumalla
2022-03-07  6:51 ` Gao, DaxueX [this message]
2022-03-10  1:35 ` Jiang, YuX
2022-03-10  8:48   ` Jerin Jacob
2022-03-16  3:32     ` Gao, DaxueX
2022-03-16  4:42       ` Jerin Jacob
2022-03-16 12:41       ` Kevin Traynor

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=CO1PR11MB5011E6BB28B9EC93090363059D089@CO1PR11MB5011.namprd11.prod.outlook.com \
    --to=daxuex.gao@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=rkudurumalla@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=stable@dpdk.org \
    /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).