dwarves.vger.kernel.org archive mirror
 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
Cc: Julia Kartseva <hex-b10kYP2dOMg@public.gmane.org>,
	andriin-b10kYP2dOMg@public.gmane.org
Subject: [PATCH 0/2] pahole: fix maybe-uninitialized and rpm build
Date: Thu, 16 Jan 2020 16:59:11 -0800	[thread overview]
Message-ID: <cover.1579221668.git.hex@fb.com> (raw)

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

Fix issues encountered while builing RPM w/ v1.16:
- maybe uninitialized variable in ‘pahole_stealer' function
- malformed date in dwarves.spec changelog causing rpm build failure

Arnaldo, I wonder if we can have v1.16 package bump in the distros sooner?
Thanks!

Julia Kartseva (2):
  pahole: fix compiler warning
  pahole: fix changelog date in dwarves.spec

 pahole.c               | 2 +-
 rpm/SPECS/dwarves.spec | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
2.17.1

             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 Yulia Kartseva [this message]
     [not found] ` <cover.1579221668.git.hex-b10kYP2dOMg@public.gmane.org>
2020-01-17  0:59   ` [PATCH 1/2] pahole: fix compiler warning Yulia Kartseva
     [not found]     ` <d0b9a8c3bd459fb41f9b4dfb80d5a5972b5c2949.1579221668.git.hex-b10kYP2dOMg@public.gmane.org>
2020-01-17 16:28       ` 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=cover.1579221668.git.hex@fb.com \
    --to=hex-b10kyp2domg@public.gmane.org \
    --cc=acme-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=andriin-b10kYP2dOMg@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 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).