From: Alan Modra <amodra@gmail.com>
To: tbsaunde+binutils@tbsaunde.org
Cc: binutils@sourceware.org
Subject: Re: [PATCH 2/2] rx: make field type enum
Date: Wed, 18 May 2016 04:14:00 -0000 [thread overview]
Message-ID: <20160518041316.GK24091@bubble.grove.modra.org> (raw)
In-Reply-To: <1463541902-11708-2-git-send-email-tbsaunde+binutils@tbsaunde.org>
On Tue, May 17, 2016 at 11:25:02PM -0400, tbsaunde+binutils@tbsaunde.org wrote:
> * config/tc-rx.c (struct cpu_type): Change the type of a field from
> int to enum rx_cpu_types.
OK, but
> --- a/gas/config/tc-rx.c
> +++ b/gas/config/tc-rx.c
> @@ -109,7 +109,7 @@ size_t md_longopts_size = sizeof (md_longopts);
> struct cpu_type
> {
> const char *cpu_name;
> - int type;
> +enum rx_cpu_types type;
> };
Formatting.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2016-05-18 4:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 3:25 [PATCH 1/2] change the type of some fields to bfd_reloc_code_real_type tbsaunde+binutils
2016-05-18 3:25 ` [PATCH 2/2] rx: make field type enum tbsaunde+binutils
2016-05-18 4:14 ` Alan Modra [this message]
2016-05-18 4:13 ` [PATCH 1/2] change the type of some fields to bfd_reloc_code_real_type Alan Modra
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=20160518041316.GK24091@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=tbsaunde+binutils@tbsaunde.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).