public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: David Guillen Fandos <david@davidgf.net>
To: binutils@sourceware.org, macro@orcam.me.uk, xuchenghua@loongson.cn
Subject: Re: [PATCH 0/3] Add support for MIPS Allegrex
Date: Tue, 25 Apr 2023 19:57:43 +0200	[thread overview]
Message-ID: <CADQAGRNTMsd_qqAXyGTLUFe78gY0fYhCDSw3fyAqVxc9kAQ72w@mail.gmail.com> (raw)
In-Reply-To: <20230328230249.274759-1-david@davidgf.es>

El mié, 29 mar 2023 a las 1:02, <david@davidgf.es> escribió:
>
> From: David Guillen Fandos <david@davidgf.net>
>
> These patches add minimal support for MIPS Allegrex CPU (present in
> Sony's Playstation Portable devices). They provide the bare minimum
> needed for a port. In particular they enable GCC support for the CPU.
>
> I tried to keep the patches small and readable, however the testsuite
> requires some rather lengthy files.

Hello Maciej W. Rozycki and Chenghua Xu,

Would it be possible to get some feedback on this if you have some
time? I'd really appreciate it! Let me know if there's anything wrong,
it's the first time sending a patch to binutils.

Thank you very much!
David

  parent reply	other threads:[~2023-04-25 17:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 23:02 david
2023-03-28 23:02 ` [PATCH 1/3] Add Allegrex CPU as a MIPS2-based CPU david
2023-05-06 23:11   ` Maciej W. Rozycki
2023-03-28 23:02 ` [PATCH 2/3] Add rotation instructions to allegrex CPU david
2023-05-06 23:11   ` Maciej W. Rozycki
2023-03-28 23:02 ` [PATCH 3/3] Adding more instructions to Allegrex CPU david
2023-05-06 23:11   ` Maciej W. Rozycki
2023-04-25 17:57 ` David Guillen Fandos [this message]
2023-04-25 22:15   ` [PATCH 0/3] Add support for MIPS Allegrex Maciej W. Rozycki
2023-05-06  8:03     ` David Guillen Fandos
2023-05-06 23:14       ` Maciej W. Rozycki

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=CADQAGRNTMsd_qqAXyGTLUFe78gY0fYhCDSw3fyAqVxc9kAQ72w@mail.gmail.com \
    --to=david@davidgf.net \
    --cc=binutils@sourceware.org \
    --cc=macro@orcam.me.uk \
    --cc=xuchenghua@loongson.cn \
    /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).