From: Michael Eager <eager@eagercon.com>
To: Gopi Kumar Bulusu <gopi@sankhya.com>, binutils@sourceware.org
Cc: Mark Hatle <mark.hatle@amd.com>, "Misra, Aayush" <Aayush.Misra@amd.com>
Subject: Re: [PATCH v1] Microblaze: Widen mask used in opcodes/microblaze-dis.c
Date: Mon, 6 Jan 2025 06:05:11 -0800 [thread overview]
Message-ID: <26d16a1d-62f7-426c-9326-31d94983302a@eagercon.com> (raw)
In-Reply-To: <CAL1P33zxd3_KygaUQ--=sCT8F2u3yHaHbMdyGw=fOqJLUxNEfw@mail.gmail.com>
Gopi --
I'm out of the office until Jan 16. I'll apply the patch when I return.
I presume that the incorrect address calcluation only happened on 64-bit
hosts.
On 1/5/25 11:29 PM, Gopi Kumar Bulusu wrote:
>
> From: Michael Eager <eager@eagercon.com <mailto:eager@eagercon.com>>
> To: binutils@sourceware.org <mailto:binutils@sourceware.org>
> Date: Sat, 4 Jan 2025 14:47:43 -0800
> Subject: Re: [PATCH v1] Microblaze: Widen mask used in opcodes/
> microblaze-dis.c
> On 12/31/24 9:26 PM, Gopi Kumar Bulusu wrote:
>
> Hi Gopi --
>
> Do you have write access to the Binutils repo?
>
> If you do, this patch is OK to check in. Please add a comment
> in the git log.
>
> If you don't, I'll apply this when I have an opportunity.
>
>
> Hello Mike,
>
> I don't have write access.
>
> Appreciate your help.
> dhanyavadam
> gopi
>
--
Michael Eager
next prev parent reply other threads:[~2025-01-06 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12.1736078404.564777.binutils@sourceware.org>
2025-01-06 7:29 ` Gopi Kumar Bulusu
2025-01-06 14:05 ` Michael Eager [this message]
2025-01-07 4:41 ` Gopi Kumar Bulusu
2025-01-27 1:50 ` [PATCH v1] [ping] " Gopi Kumar Bulusu
2025-01-01 5:26 [PATCH v1] " Gopi Kumar Bulusu
2025-01-04 22:47 ` Michael Eager
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=26d16a1d-62f7-426c-9326-31d94983302a@eagercon.com \
--to=eager@eagercon.com \
--cc=Aayush.Misra@amd.com \
--cc=binutils@sourceware.org \
--cc=gopi@sankhya.com \
--cc=mark.hatle@amd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).