From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/7] gdb: Use NULL instead of 0 for pointer comparison.
Date: Thu, 26 Nov 2015 12:37:00 -0000 [thread overview]
Message-ID: <5656FCF2.9080307@redhat.com> (raw)
In-Reply-To: <ca67590dc936ca9fb3290a5352adbbd0b20004ff.1448411121.git.andrew.burgess@embecosm.com>
On 11/25/2015 12:34 AM, Andrew Burgess wrote:
> Small code cleanup, use NULL instead of 0 when checking pointers. There
> should be no user visible changes after this commit.
>
> gdb/ChangeLog:
>
> * cli/cli-cmds.c (list_command): Use NULL instead of 0 when
> checking pointers.
OK. Please feel free to push fixes like these as obvious.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-11-26 12:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 0:34 [PATCH 0/7] Minor changes to 'list' command Andrew Burgess
2015-11-25 0:34 ` [PATCH 2/7] gdb: Use NULL instead of 0 for pointer comparison Andrew Burgess
2015-11-26 12:37 ` Pedro Alves [this message]
2015-11-25 0:34 ` [PATCH 6/7] gdb: Add an error when 'list -' reaches the start of a file Andrew Burgess
2015-11-26 12:38 ` Pedro Alves
2015-11-25 0:34 ` [PATCH 7/7] gdb: Extend help text for 'list' command Andrew Burgess
2015-11-26 12:38 ` Pedro Alves
2015-12-10 10:08 ` Andrew Burgess
2015-12-10 16:24 ` Eli Zaretskii
2015-11-25 0:34 ` [PATCH 5/7] gdb: 'list' command, tweak handling of +/- arguments Andrew Burgess
2015-11-26 12:38 ` Pedro Alves
2015-11-25 0:34 ` [PATCH 3/7] gdb: Small code restructure for list_command Andrew Burgess
2015-11-26 12:37 ` Pedro Alves
2015-11-25 0:34 ` [PATCH 4/7] gdb: Make test names unique in list.exp Andrew Burgess
2015-11-26 12:37 ` Pedro Alves
2015-11-25 0:34 ` [PATCH 1/7] gdb: Make lines_to_list variable static Andrew Burgess
2015-11-26 12:37 ` Pedro Alves
2015-12-11 23:28 ` [PATCH 0/7] Minor changes to 'list' command Andrew Burgess
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=5656FCF2.9080307@redhat.com \
--to=palves@redhat.com \
--cc=andrew.burgess@embecosm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).