From: Paul Hua <paul.hua.gm@gmail.com>
To: Faraz Shahbazker <fshahbazker@wavecomp.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH 2/2] [MIPS] Add i6500 CPU and fix i6400 default ASEs
Date: Sat, 13 Apr 2019 08:35:00 -0000 [thread overview]
Message-ID: <CAKjxQH=d+4FNOzq6R-NbbWNfH5pLoESvdjPBexgnWqxZn+CixA@mail.gmail.com> (raw)
In-Reply-To: <13442c15-2fe1-662e-dbab-f02688d891fc@wavecomp.com>
Hi,
Finally, I applied the patch.
ok for committed.
On Sat, Apr 13, 2019 at 12:55 PM Faraz Shahbazker
<fshahbazker@wavecomp.com> wrote:
>
> Hi Paul,
>
> On 04/12/2019 07:06 PM, Paul Hua wrote:
> > Hi:
> > Which commit is your patch based on?
> >
> > I based on 35add35e85c21f02e3e5808273cb77b24069b0aa, output is :
> >
> > Can you try the same commit ?
> > ps: My configure option is : ../configure --prefix=/opt/binutils
> > --target=mips64el-linux-gnu, then make ; make check.
>
> I tried with the same commit as well as HEAD. I tried the file generated
> using 'Save as' in thunderbird and the patch from the mailing list
> digest dated 9th April and with 'raw text' downloaded from the mailing
> list archives. All 3 applied cleanly and gave identical test results.
> The only difference is that I used 'git am' to apply the patches.
>
> Regards,
> Faraz
next prev parent reply other threads:[~2019-04-13 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 20:40 [PATCH 1/2] [MIPS] Apply ASE information for the selected processor Faraz Shahbazker
2019-04-09 20:40 ` [PATCH 2/2] [MIPS] Add i6500 CPU and fix i6400 default ASEs Faraz Shahbazker
2019-04-11 2:44 ` Paul Hua
2019-04-11 16:52 ` Faraz Shahbazker
2019-04-12 1:14 ` Paul Hua
2019-04-12 2:09 ` Faraz Shahbazker
2019-04-13 2:06 ` Paul Hua
2019-04-13 4:55 ` Faraz Shahbazker
2019-04-13 8:35 ` Paul Hua [this message]
2019-04-13 8:32 ` [PATCH 1/2] [MIPS] Apply ASE information for the selected processor Paul Hua
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='CAKjxQH=d+4FNOzq6R-NbbWNfH5pLoESvdjPBexgnWqxZn+CixA@mail.gmail.com' \
--to=paul.hua.gm@gmail.com \
--cc=binutils@sourceware.org \
--cc=fshahbazker@wavecomp.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).