From: Michael Eager <eager@eagerm.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] bitpos: Expand type_field_bitpos to LONGEST and type.length to ULONGEST
Date: Mon, 06 Aug 2012 14:13:00 -0000 [thread overview]
Message-ID: <501FD112.5070509@eagerm.com> (raw)
In-Reply-To: <20120806083524.08b39f37@spoyarek>
On 08/05/2012 08:05 PM, Siddhesh Poyarekar wrote:
> On Sun, 05 Aug 2012 04:42:43 -0700, Michael wrote:
>> The ChangeLog mentions a modification to microblaze-tdep.c, but the
>> patch does not contain any changes to this file.
>>
>
> Oh boy, I took the wrong diff from my repo when posting the patch -- I
> had the patch in two changesets. Attached is the real patch for this.
> ChangeLog added once again for review benefit.
Approved for MicroBlaze. And glad we caught the mixup.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2012-08-06 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 19:25 Siddhesh Poyarekar
2012-08-05 11:42 ` Michael Eager
2012-08-06 3:07 ` Siddhesh Poyarekar
2012-08-06 14:13 ` Michael Eager [this message]
2012-08-22 17:15 ` Sergio Durigan Junior
2012-08-22 20:41 ` Sergio Durigan Junior
2012-08-23 10:54 ` Siddhesh Poyarekar
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=501FD112.5070509@eagerm.com \
--to=eager@eagerm.com \
--cc=gdb-patches@sourceware.org \
--cc=siddhesh@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