From: Mike Frysinger <vapier@gentoo.org>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v2 1/4] gdb: Add tdesc_find_register functions
Date: Sat, 26 Nov 2016 22:40:52 -0800 [thread overview]
Message-ID: <20161127064052.GV21655@vapier.lan> (raw)
In-Reply-To: <ffdc788c10996edca2b068acd5d43fda1592be01.1480216015.git.shorne@gmail.com>
On 27 Nov 2016 15:16, Stafford Horne wrote:
> +/* Search FEATURE for a register REGNO and return its name. */
GNU style puts two spaces after periods
> +char *
> +tdesc_find_register_name (const struct tdesc_feature *feature,
> + int regno)
> +char *
> +tdesc_find_register_group_name (const struct tdesc_feature *feature,
> + int regno)
seems like return values for both of these should be const
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20161126/03586987/attachment.sig>
next prev parent reply other threads:[~2016-11-27 6:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 6:16 [OpenRISC] [PATCH v2 0/4] gdb: Port for OpenRISC Stafford Horne
2016-11-27 6:16 ` [OpenRISC] [PATCH v2 1/4] gdb: Add tdesc_find_register functions Stafford Horne
2016-11-27 6:40 ` Mike Frysinger [this message]
2016-11-27 7:09 ` Stafford Horne
2016-11-27 6:16 ` [OpenRISC] [PATCH v2 2/4] gdb: Add OpenRISC or1k and or1knd target support Stafford Horne
2016-11-29 10:06 ` Yao Qi
2016-12-22 16:11 ` Stafford Horne
2016-11-27 6:16 ` [OpenRISC] [PATCH v2 3/4] gdb: testsuite: Add or1k l.nop inscruction Stafford Horne
2016-11-27 6:16 ` [OpenRISC] [PATCH v2 4/4] Add gdb for or1k build Stafford Horne
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=20161127064052.GV21655@vapier.lan \
--to=vapier@gentoo.org \
--cc=openrisc@lists.librecores.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