From: Thomas Huth <huth@tuxfamily.org>
To: qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: Thomas Huth <thuth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/7] Remove more unused functions
Date: Sun, 26 Apr 2015 15:17:03 +0200 [thread overview]
Message-ID: <20150426151703.161075bb@tpl530> (raw)
In-Reply-To: <20150318122235.7eb71f08@oc7435384737.ibm.com>
Am Wed, 18 Mar 2015 12:22:35 +0100
schrieb Thomas Huth <thuth@linux.vnet.ibm.com>:
>
> Here are some more patches to remove completely unused functions
> from QEMU. Please review carefully, some of the functions might
> still get usefull in the future again, so if you discover one,
> please let me know, then I'll remove it from the patch series
> again.
>
> v2: Changed series according to review comment from v1:
> - Dropped the patch to remove portio_list_destroy() and
> portio_list_del()
> - Keep the ARI functions in the pci patch since they might get useful
> again
>
> Thomas Huth (7):
> migration: Remove unused functions
> vmxnet: Remove unused function vmxnet_rx_pkt_get_num_frags()
> pci: Remove unused function ich9_d2pbr_init()
> monitor: Remove unused functions
> usb: Remove unused functions
> util: Remove unused functions
> Remove various unused functions
Ping! Now that 2.3.0 (congrats!) has been tagged, could somebody
(Michael via qemu-trivial tree?) please pick up patches 2 to 7? As far
as I know, there haven't been any complaints about them anymore, so I
think it should be ok to include them.
(patch 1 has already been included via the migration tree, so that's
already fine)
Cheers,
Thomas
next parent reply other threads:[~2015-04-26 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150318122235.7eb71f08@oc7435384737.ibm.com>
2015-04-26 13:17 ` Thomas Huth [this message]
[not found] <20150428082846.1348066e@thh440s>
2015-04-28 6:38 ` [Qemu-devel] [PATCH v2 0/7] Remove more unused functions Thomas Huth
2015-04-29 6:17 ` Michael Tokarev
2015-03-14 6:19 Thomas Huth
2015-04-27 11:27 ` Michael Tokarev
2015-04-27 18:09 ` Stefan Weil
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=20150426151703.161075bb@tpl530 \
--to=huth@tuxfamily.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@linux.vnet.ibm.com \
/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).