From: Pedro Alves <palves@redhat.com>
To: Ajit Kumar Agarwal <ajit.kumar.agarwal@xilinx.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Michael Eager <eager@eagercon.com>,
Vinod Kathail <vinodk@xilinx.com>,
Vidhumouli Hunsigida <vidhum@xilinx.com>,
Nagaraju Mekala <nmekala@xilinx.com>
Subject: Re: [Patch, microblaze]: Fix for remote G Packet message too long error for baremetal.
Date: Wed, 18 Jun 2014 15:30:00 -0000 [thread overview]
Message-ID: <53A1B0A0.3060005@redhat.com> (raw)
In-Reply-To: <53A1ABF0.9080004@redhat.com>
Also, I forgot to say -- new xml target features should be documented
in the manual.
--
Pedro Alves
next prev parent reply other threads:[~2014-06-18 15:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 8:56 Ajit Kumar Agarwal
2014-06-12 14:52 ` Michael Eager
2014-06-17 11:17 ` Pedro Alves
2014-06-18 11:06 ` Ajit Kumar Agarwal
2014-06-18 14:58 ` Michael Eager
2014-06-18 15:10 ` Pedro Alves
2014-06-18 15:30 ` Pedro Alves [this message]
2014-06-18 15:40 ` Ajit Kumar Agarwal
2014-06-18 15:54 ` Pedro Alves
2014-06-18 15:57 ` Ajit Kumar Agarwal
2014-06-18 19:56 ` Ajit Kumar Agarwal
2014-06-23 13:18 ` Pedro Alves
2014-06-23 19:36 ` Ajit Kumar Agarwal
2014-06-24 9:13 ` Pedro Alves
2014-06-24 10:28 ` Ajit Kumar Agarwal
2014-06-24 12:06 ` Pedro Alves
2014-06-24 12:31 ` Ajit Kumar Agarwal
2014-06-24 12:46 ` Pedro Alves
2014-06-24 13:27 ` Ajit Kumar Agarwal
2014-06-30 10:32 ` Ajit Kumar Agarwal
2014-06-30 10:55 ` Pedro Alves
2014-06-30 11:13 ` Ajit Kumar Agarwal
2014-06-30 11:23 ` Pedro Alves
2014-06-30 16:29 ` Ajit Kumar Agarwal
2014-07-01 19:36 ` Ajit Kumar Agarwal
2014-07-20 12:57 ` Michael Eager
2014-06-30 14:47 ` Michael Eager
2014-07-01 16:07 ` Ajit Kumar Agarwal
2014-07-01 16:46 ` Michael Eager
2014-07-02 10:40 ` Ajit Kumar Agarwal
2014-06-24 14:11 ` Michael Eager
2014-06-25 13:00 ` Ajit Kumar Agarwal
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=53A1B0A0.3060005@redhat.com \
--to=palves@redhat.com \
--cc=ajit.kumar.agarwal@xilinx.com \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
--cc=nmekala@xilinx.com \
--cc=vidhum@xilinx.com \
--cc=vinodk@xilinx.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