public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: David Guillen <david@davidgf.es>, binutils@sourceware.org
Subject: Re: Upstream PSP support in binutils
Date: Fri, 21 Oct 2022 11:47:18 +0100	[thread overview]
Message-ID: <0deaab53-e106-c5e6-6a3a-5f9bbe32af04@redhat.com> (raw)
In-Reply-To: <CADQAGROjk095xxAA04bkXcBpfOJVsuqu0WdfMHELMM4LW9vAhA@mail.gmail.com>

Hi David,

> I'm reaching out to know how much interest there'd be to add upstream
> support in binutils for the Sony PSP CPU. Before patches are crafted and
> tests are written, I'd like to know if this is something that you guys
> would consider merging. I'd be doing the work but you would need to help
> reviewing and merging it of course :)

Of course. :-)

The short answer is "yes", but with a caveat.  Or two.  The first being that
someone needs to volunteer to act as a maintainer for the port.  They need
to be willing to read the mailing list, handle PSP specific bug reports,
answer questions about the port, and generally make sure that it carries on
working as the years progress.

The other caveat is that ideally the copyright for the patches should be
assigned to the FSF.  (Strictly speaking we are now accepting DCO signed
contributions as well, but for a new port I would feel happier with a
copyright assignment).  Plus they should follow the GNU Coding Standards,
not break other ports, have a testsuite, and all the usual things for a
contribution to the GNU Binutils.

Cheers
   Nick



  reply	other threads:[~2022-10-21 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 23:18 David Guillen
2022-10-21 10:47 ` Nick Clifton [this message]
2022-11-15 21:17   ` David Guillen Fandos
2022-11-16 11:07     ` Nick Clifton
2022-12-09 21:59       ` David Guillen Fandos

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=0deaab53-e106-c5e6-6a3a-5f9bbe32af04@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=david@davidgf.es \
    /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).