From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: [PATCH 2/2] Fix doc of AVR-specific command "info io_registers"
Date: Tue, 03 Dec 2019 06:20:00 -0000 [thread overview]
Message-ID: <20191203062031.2844278-2-simon.marchi@polymtl.ca> (raw)
In-Reply-To: <20191203062031.2844278-1-simon.marchi@polymtl.ca>
Running the selftests on an all-targets build, I get:
Running selftest help_doc_invariants.
help doc broken invariant: command 'info io_registers' help doc first line is not terminated with a '.' character
Self test failed: self-test failed at /home/simark/src/binutils-gdb/gdb/unittests/help-doc-selftests.c:95
Add a period at the end of the doc of that command, and make it a bit
nicer in general.
gdb/ChangeLog:
* avr-tdep.c (_initialize_avr_tdep): Improve help of command
"info io_registers".
---
gdb/avr-tdep.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/avr-tdep.c b/gdb/avr-tdep.c
index 6d11ee1618cc..61a0a5dd52ea 100644
--- a/gdb/avr-tdep.c
+++ b/gdb/avr-tdep.c
@@ -1629,5 +1629,5 @@ _initialize_avr_tdep (void)
io_registers' to signify it is not available on other platforms. */
add_info ("io_registers", avr_io_reg_read_command,
- _("query remote avr target for io space register values"));
+ _("Query remote AVR target for I/O space register values."));
}
--
2.24.0
next prev parent reply other threads:[~2019-12-03 6:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 6:20 [PATCH 1/2] Fix regcache::cooked_read_test selftest for mep Simon Marchi
2019-12-03 6:20 ` Simon Marchi [this message]
2019-12-04 17:49 ` [PATCH 2/2] Fix doc of AVR-specific command "info io_registers" Tom Tromey
2019-12-04 17:49 ` [PATCH 1/2] Fix regcache::cooked_read_test selftest for mep Tom Tromey
2019-12-04 18:48 ` Simon Marchi
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=20191203062031.2844278-2-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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).