From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Andrzej Ostruszka <amo@semihalf.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Jerin Jacob Kollanukkaran" <jerinj@marvell.com>
Cc: "mattias.ronnblom@ericsson.com" <mattias.ronnblom@ericsson.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
Andrzej Ostruszka <aostruszka@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2 04/10] event/octeontx2: fix maybe-uninitialized warnings for LTO build
Date: Sat, 12 Oct 2019 15:43:14 +0000 [thread overview]
Message-ID: <CY4PR1801MB18635787C76E346ED29B4AB0DE960@CY4PR1801MB1863.namprd18.prod.outlook.com> (raw)
>During LTO build compiler reports some 'false positive' warnings about
>variables being possibly used uninitialized. This patch silences these
>warnings.
>
>Signed-off-by: Andrzej Ostruszka <aostruszka@marvell.com>
Acked-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
>---
> drivers/event/octeontx2/otx2_tim_worker.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/event/octeontx2/otx2_tim_worker.h
>b/drivers/event/octeontx2/otx2_tim_worker.h
>index b193e2cab..50db6543c 100644
>--- a/drivers/event/octeontx2/otx2_tim_worker.h
>+++ b/drivers/event/octeontx2/otx2_tim_worker.h
>@@ -337,7 +337,7 @@ tim_add_entry_brst(struct otx2_tim_ring *
>const tim_ring,
> const struct otx2_tim_ent *ents,
> const uint16_t nb_timers, const uint8_t flags)
> {
>- struct otx2_tim_ent *chunk;
>+ struct otx2_tim_ent *chunk = NULL;
> struct otx2_tim_bkt *bkt;
> uint16_t chunk_remainder;
> uint16_t index = 0;
>--
>2.17.1
next reply other threads:[~2019-10-12 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 15:43 Pavan Nikhilesh Bhagavatula [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-17 7:57 [dpdk-dev] [PATCH v2 00/10] Add an option to use LTO for DPDK build Andrzej Ostruszka
2019-09-17 7:57 ` [dpdk-dev] [PATCH v2 04/10] event/octeontx2: fix maybe-uninitialized warnings for LTO build Andrzej Ostruszka
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=CY4PR1801MB18635787C76E346ED29B4AB0DE960@CY4PR1801MB1863.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.com \
--cc=amo@semihalf.com \
--cc=aostruszka@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=stephen@networkplumber.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).