From: Gerd Hoffmann <kraxel@redhat.com>
To: Thomas Huth <thuth@linux.vnet.ibm.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH 2/4] ui/console: Removed unused functions
Date: Tue, 17 Feb 2015 09:21:57 +0100 [thread overview]
Message-ID: <1424161317.6014.14.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <1424122891-9390-3-git-send-email-thuth@linux.vnet.ibm.com>
On Mo, 2015-02-16 at 22:41 +0100, Thomas Huth wrote:
> Remove dpy_gfx_update_dirty(), qemu_console_get_head(),
> qemu_console_get_ui_info(), qemu_console_get_width(),
> qemu_console_get_height(), emu_console_displaystate(),
> qemu_different_endianness_pixelformat(), void cpkey(),
> qemu_pixman_linebuf_copy(), qemu_pixman_color(),
> emu_remove_kbd_event_handler() and vnc_stop_worker_thread()
> since they are completely unused.
Vetoing this one. Some of them belong to work-in-progress bits and
should not be removed.
Also I think this kind of cleanup should be splitted into smaller
pieces, so it is easier to get specific bits back via "git revert"
should the need arise.
> -void dpy_gfx_update_dirty(QemuConsole *con,
Keep.
> -QemuUIInfo *qemu_console_get_ui_info(QemuConsole *con)
Keep.
> -int qemu_console_get_width(QemuConsole *con, int fallback)
> -int qemu_console_get_height(QemuConsole *con, int fallback)
Hmm, not sure. Separate patch please.
> -DisplayState *qemu_console_displaystate(QemuConsole *console)
Ok.
> -PixelFormat qemu_different_endianness_pixelformat(int bpp)
Ok.
> -void cpkey(register unsigned long *into)
Ok.
> -void qemu_remove_kbd_event_handler(QEMUPutKbdEntry *entry)
Ok.
> -void qemu_input_handler_deactivate(QemuInputHandlerState *s)
Hmm, might be needed in the future. Separate patch please.
> -/* copy linebuf to framebuffer */
> -void qemu_pixman_linebuf_copy(pixman_image_t *fb, int width, int x, int y,
> - pixman_image_t *linebuf)
> -{
> - pixman_image_composite(PIXMAN_OP_SRC, linebuf, NULL, fb,
> - 0, 0, 0, 0, x, y, width, 1);
> -}
Keep.
> -pixman_color_t qemu_pixman_color(PixelFormat *pf, uint32_t color)
> -{
> - pixman_color_t c;
> -
> - c.red = ((color & pf->rmask) >> pf->rshift) << (16 - pf->rbits);
> - c.green = ((color & pf->gmask) >> pf->gshift) << (16 - pf->gbits);
> - c.blue = ((color & pf->bmask) >> pf->bshift) << (16 - pf->bbits);
> - c.alpha = ((color & pf->amask) >> pf->ashift) << (16 - pf->abits);
> - return c;
> -}
Not sure. Separate patch please.
> -void vnc_stop_worker_thread(void)
Probably ok. Separate patch would be nice.
cheers,
Gerd
next prev parent reply other threads:[~2015-02-17 8:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 21:41 [Qemu-devel] [PATCH 0/4] Remove unused functions Thomas Huth
2015-02-16 21:41 ` [Qemu-devel] [PATCH 1/4] migration: " Thomas Huth
2015-02-16 21:41 ` [Qemu-devel] [PATCH 2/4] ui/console: Removed " Thomas Huth
2015-02-17 8:21 ` Gerd Hoffmann [this message]
2015-02-16 21:41 ` [Qemu-devel] [PATCH 3/4] util: Remove " Thomas Huth
2015-02-17 8:55 ` Markus Armbruster
2015-02-17 9:52 ` Thomas Huth
2015-02-16 21:41 ` [Qemu-devel] [PATCH 4/4] block: " Thomas Huth
2015-02-16 22:26 ` Max Reitz
2015-02-17 8:15 ` Thomas Huth
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=1424161317.6014.14.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=aliguori@amazon.com \
--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).