All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yulia Kartseva <hex-b10kYP2dOMg@public.gmane.org>
To: dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	acme-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	hex-b10kYP2dOMg@public.gmane.org
Subject: [PATCH 1/2] pahole: fix compiler warning
Date: Thu, 16 Jan 2020 16:59:12 -0800	[thread overview]
Message-ID: <d0b9a8c3bd459fb41f9b4dfb80d5a5972b5c2949.1579221668.git.hex@fb.com> (raw)
In-Reply-To: <cover.1579221668.git.hex-b10kYP2dOMg@public.gmane.org>

From: Julia Kartseva <hex-b10kYP2dOMg@public.gmane.org>

Signed-off-by: Julia Kartseva <hex-b10kYP2dOMg@public.gmane.org>
---
 pahole.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pahole.c b/pahole.c
index 829c9ab..7ac49c2 100644
--- a/pahole.c
+++ b/pahole.c
@@ -684,8 +684,8 @@ static void print_structs_with_pointer_to(struct cu *cu, uint32_t type)
 	uint32_t id;
 
 	cu__for_each_struct_or_union(cu, id, pos) {
+		struct structure *str = NULL;
 		bool looked = false;
-		struct structure *str;
 
 		if (pos->type.namespace.name == 0)
 			continue;
-- 
2.17.1

  parent reply	other threads:[~2020-01-17  0:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17  0:59 [PATCH 0/2] pahole: fix maybe-uninitialized and rpm build Yulia Kartseva
     [not found] ` <cover.1579221668.git.hex-b10kYP2dOMg@public.gmane.org>
2020-01-17  0:59   ` Yulia Kartseva [this message]
     [not found]     ` <d0b9a8c3bd459fb41f9b4dfb80d5a5972b5c2949.1579221668.git.hex-b10kYP2dOMg@public.gmane.org>
2020-01-17 16:28       ` [PATCH 1/2] pahole: fix compiler warning Arnaldo Carvalho de Melo
2020-01-17  0:59   ` [PATCH 2/2] pahole: fix changelog date in dwarves.spec Yulia Kartseva
     [not found]     ` <e454b36160ba6cdc0fede26ca2ee8fe15314ae99.1579221668.git.hex-b10kYP2dOMg@public.gmane.org>
2020-01-17 16:31       ` Arnaldo Carvalho de Melo

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=d0b9a8c3bd459fb41f9b4dfb80d5a5972b5c2949.1579221668.git.hex@fb.com \
    --to=hex-b10kyp2domg@public.gmane.org \
    --cc=acme-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.