From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Aleksandar Rikalo" <aleksandar.rikalo@syrmia.com>,
"Huacai Chen" <chenhuacai@kernel.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Greg Kurz" <groug@kaod.org>,
"Hervé Poussineau" <hpoussin@reactos.org>,
qemu-ppc@nongnu.org, "Aurelien Jarno" <aurelien@aurel32.net>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: [PATCH v2 0/4] hw/isa: Remove unuseful qemu_allocate_irqs() call
Date: Tue, 11 May 2021 06:06:17 +0200 [thread overview]
Message-ID: <20210511040621.2736981-1-f4bug@amsat.org> (raw)
I started to fix the LeakSanitizer error in piix4_realize(),
then looked for similar pattern and found 2 other places.
The older is i82378 (historically the first one) which then
spread.
Since v1:
- rebased
- removed vt82c686 patches
Philippe Mathieu-Daudé (4):
hw/isa/i82378: Name output IRQ as 'intr'
hw/isa/i82378: Simplify removing unuseful qemu_allocate_irqs() call
hw/isa/i82378: Rename output IRQ variable
hw/isa/piix4: Fix leak removing unuseful qemu_allocate_irqs() call
hw/isa/i82378.c | 13 +++----------
hw/isa/piix4.c | 10 +---------
hw/ppc/prep.c | 4 ++--
3 files changed, 6 insertions(+), 21 deletions(-)
--
2.26.3
next reply other threads:[~2021-05-11 4:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 4:06 Philippe Mathieu-Daudé [this message]
2021-05-11 4:06 ` [PATCH v2 1/4] hw/isa/i82378: Name output IRQ as 'intr' Philippe Mathieu-Daudé
2021-05-11 4:06 ` [PATCH v2 2/4] hw/isa/i82378: Simplify removing unuseful qemu_allocate_irqs() call Philippe Mathieu-Daudé
2021-05-11 4:06 ` [PATCH v2 3/4] hw/isa/i82378: Rename output IRQ variable Philippe Mathieu-Daudé
2021-05-11 4:06 ` [PATCH v2 4/4] hw/isa/piix4: Fix leak removing unuseful qemu_allocate_irqs() call Philippe Mathieu-Daudé
2021-11-06 15:04 ` [PATCH v2 0/4] hw/isa: Remove " Philippe Mathieu-Daudé
2021-11-06 19:13 ` BALATON Zoltan
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=20210511040621.2736981-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=aleksandar.rikalo@syrmia.com \
--cc=aurelien@aurel32.net \
--cc=chenhuacai@kernel.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=hpoussin@reactos.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).