public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Don't declare tui_init_content_element Date: Thu, 20 Jun 2019 04:28:00 -0000 [thread overview] Message-ID: <20190620042807.23339.qmail@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e6a1c5cbcb9cee5a08d814669419936ee151b19d commit e6a1c5cbcb9cee5a08d814669419936ee151b19d Author: Tom Tromey <tom@tromey.com> Date: Wed Jun 19 22:24:30 2019 -0600 Don't declare tui_init_content_element I noticed that tui_init_content_element is declared but never defined. This removes the declaration. Tested by rebuilding. (I should have merged this with the previous patch but I had forgotten that I found two of these.) gdb/ChangeLog 2019-06-19 Tom Tromey <tom@tromey.com> * tui/tui-data.h (tui_init_content_element): Don't declare. Diff: --- gdb/ChangeLog | 4 ++++ gdb/tui/tui-data.h | 2 -- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 1e30d76..18197b1 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,9 @@ 2019-06-19 Tom Tromey <tom@tromey.com> + * tui/tui-data.h (tui_init_content_element): Don't declare. + +2019-06-19 Tom Tromey <tom@tromey.com> + * tui/tui-data.h (tui_init_win_info): Don't declare. 2019-06-19 Tom de Vries <tdevries@suse.de> diff --git a/gdb/tui/tui-data.h b/gdb/tui/tui-data.h index 5673d46..c42647b 100644 --- a/gdb/tui/tui-data.h +++ b/gdb/tui/tui-data.h @@ -306,8 +306,6 @@ extern void tui_init_generic_part (struct tui_gen_win_info *); extern tui_win_content tui_alloc_content (int, enum tui_win_type); extern int tui_add_content_elements (struct tui_gen_win_info *, int); -extern void tui_init_content_element (struct tui_win_element *, - enum tui_win_type); extern void tui_free_window (struct tui_win_info *); extern void tui_free_win_content (struct tui_gen_win_info *); extern void tui_free_data_content (tui_win_content, int);
reply other threads:[~2019-06-20 4:28 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190620042807.23339.qmail@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).