Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Stafford Horne <shorne@gmail.com>
Cc: gdb-patches@sourceware.org, openrisc@lists.librecores.org,
	Franck Jullien <franck.jullien@gmail.com>
Subject: Re: [PATCH v2 1/4] gdb: Add tdesc_find_register functions
Date: Sun, 27 Nov 2016 06:42:00 -0000	[thread overview]
Message-ID: <20161127064052.GV21655@vapier.lan> (raw)
In-Reply-To: <ffdc788c10996edca2b068acd5d43fda1592be01.1480216015.git.shorne@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 416 bytes --]

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-11-27  6:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27  6:18 [PATCH v2 0/4] gdb: Port for OpenRISC Stafford Horne
2016-11-27  6:17 ` [PATCH v2 1/4] gdb: Add tdesc_find_register functions Stafford Horne
2016-11-27  6:42   ` Mike Frysinger [this message]
2016-11-27  7:09     ` Stafford Horne
2016-11-27  6:17 ` [PATCH v2 4/4] Add gdb for or1k build Stafford Horne
2016-11-27  6:17 ` [PATCH v2 3/4] gdb: testsuite: Add or1k l.nop inscruction Stafford Horne
2016-11-27  6:18 ` [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

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=franck.jullien@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=openrisc@lists.librecores.org \
    --cc=shorne@gmail.com \
    /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