From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Cleber Rosa <crosa@redhat.com>
Cc: gdb-patches@sourceware.org, cleber@redhat.com
Subject: Re: [PATCH 1/2] remote-utils.c: remove unused gdb_stdlog
Date: Mon, 01 Dec 2014 20:34:00 -0000 [thread overview]
Message-ID: <874mtfyuqq.fsf@redhat.com> (raw)
In-Reply-To: <1417449499-23681-1-git-send-email-crosa@redhat.com> (Cleber Rosa's message of "Mon, 1 Dec 2014 12:58:18 -0300")
On Monday, December 01 2014, Cleber Rosa wrote:
> It looks like this came from an attempt to mimmic gdb/main.c, which
> has gdb_stdlog, gdb_stderr, gdb_stdout, etc. But in reality, it's
> not being used on gdbserver.
Heya :-).
Thanks for sending the patch upstream. As we have already discussed on
private, this looks almost obvious to me, but let's wait for some
maintainer to approve. Meanwhile...
> Signed-off-by: Cleber Rosa <crosa@redhat.com>
We don't use Signed-off-by here, but it shouldn't do any harm to keep it
in the patch.
> ---
> gdb/gdbserver/ChangeLog | 4 ++++
> gdb/gdbserver/remote-utils.c | 1 -
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/gdbserver/ChangeLog b/gdb/gdbserver/ChangeLog
> index e378a5f..0e110e7 100644
> --- a/gdb/gdbserver/ChangeLog
> +++ b/gdb/gdbserver/ChangeLog
> @@ -1,3 +1,7 @@
> +2014-12-01 Cleber Rosa <cleber@redhat.com>
> +
> + * remote-utils.c: Remove unused variable.
Every entry in the ChangeLog should be indented using TABs, and not
spaces. You could also specify *which* unused variable you are
removing. Thus:
* remote-utils.c: Remove unused variable "gdb_stdlog".
> +
> 2014-11-28 Yao Qi <yao@codesourcery.com>
>
> * configure.ac(AC_CHECK_FUNCS): Remove readlink.
> diff --git a/gdb/gdbserver/remote-utils.c b/gdb/gdbserver/remote-utils.c
> index 373fc15..442e94e 100644
> --- a/gdb/gdbserver/remote-utils.c
> +++ b/gdb/gdbserver/remote-utils.c
> @@ -100,7 +100,6 @@ struct sym_cache
> };
>
> int remote_debug = 0;
> -struct ui_file *gdb_stdlog;
>
> static int remote_is_stdio = 0;
>
> --
> 1.9.3
Thanks,
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2014-12-01 20:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 15:58 Cleber Rosa
2014-12-01 15:58 ` [PATCH 2/2] Function attributes: use shorter versions of the format macros Cleber Rosa
2014-12-01 20:39 ` Sergio Durigan Junior
2014-12-03 10:31 ` Joel Brobecker
2014-12-04 13:29 ` Cleber Rosa
2014-12-11 18:51 ` [v2,1/2] remote-utils.c: remove unused gdb_stdlog Cleber Rosa
2014-12-11 18:51 ` [v2,2/2] Function attributes: use shorter versions of the format macros Cleber Rosa
2014-12-12 11:51 ` Pedro Alves
2014-12-13 16:21 ` Cleber Rosa
2014-12-01 20:34 ` Sergio Durigan Junior [this message]
2014-12-03 10:12 ` [PATCH 1/2] remote-utils.c: remove unused gdb_stdlog Joel Brobecker
2014-12-04 16:49 ` Sergio Durigan Junior
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=874mtfyuqq.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=cleber@redhat.com \
--cc=crosa@redhat.com \
--cc=gdb-patches@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: 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