Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: nick clifton <nickc@redhat.com>
To: Kaushik Phatak <Kaushik.Phatak@kpitcummins.com>
Cc: Tom Tromey <tromey@redhat.com>, Pedro Alves <palves@redhat.com>,
	       "binutils@sourceware.org" <binutils@sourceware.org>,
	       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	       Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFA] New port: CR16: BFD Changes required by the gdb port
Date: Mon, 07 Jan 2013 15:11:00 -0000	[thread overview]
Message-ID: <50EAE4E0.4000707@redhat.com> (raw)
In-Reply-To: <C6CA53A2A46BA7469348BDBD663AB65848564F47@KCHJEXMB02.kpit.com>

Hi Kaushik,

> Please find below a patch that adds similar prefix for make_instruction
> and match_opcode. I have re-based this against gdb-7.5.50.20130103.
> Also fixed a minor typo (doewsn't -> doesn't)

Thanks - I have applied your patch along with these changelog entries.

Cheers
   Nick

opcodes/ChangeLog
2013-01-07  Kaushik Phatak  <kaushik.phatak@kpitcummins.com>

	* cr16-dis.c (make_instruction): Rename to cr16_make_instruction.
	(match_opcode): Rename to cr16_match_opcode.

include/opcodes/ChangeLog
2013-01-07  Kaushik Phatak  <kaushik.phatak@kpitcummins.com>

	* cr16.h (make_instruction): Rename to cr16_make_instruction.
	(match_opcode): Rename to cr16_match_opcode.


  reply	other threads:[~2013-01-07 15:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26  7:04 Kaushik Phatak
2012-12-14 18:52 ` Pedro Alves
2012-12-28 12:18   ` Kaushik Phatak
2013-01-02 13:14     ` nick clifton
2013-01-03 11:16       ` Kaushik Phatak
2013-01-07 15:11         ` nick clifton [this message]
2013-01-08 11:24           ` Kaushik Phatak
2013-01-08 17:54             ` Pedro Alves
2013-01-15  9:24               ` Kaushik Phatak
2013-01-02 14:19     ` Tom Tromey

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=50EAE4E0.4000707@redhat.com \
    --to=nickc@redhat.com \
    --cc=Kaushik.Phatak@kpitcummins.com \
    --cc=binutils@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=tromey@redhat.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