public inbox for test-list@sourceware.org
help / color / mirror / Atom feed
From: Christopher Faylor <cgf000@gmail.com>
To: "Fredrik Noring" <noring@cgf.cx>,
	"Maciej W. Rozycki" <macro@cgf.cx>,
	gcc-patches@cgf.cx, "Jürgen Urban" <JuergenUrban@cgf.cx>,
	test-list@sourceware.org
Subject: Re: [PATCH] MIPS: Add `-mfix-r5900' option for the R5900 short loop erratum
Date: Sun, 16 Dec 2018 20:38:00 -0000	[thread overview]
Message-ID: <CALOBT3CZWJMnjhWoQL7A_-7S6BqF5jFHQC82txBg0RhmOQFn9w@mail.gmail.com> (raw)
In-Reply-To: <00ed01d4787b$caae0620$600a1260$@gmail.com>

On Sun, Dec 16, 2018 at 3:29 PM <mfortune@gmail.com> wrote:
>
> Hi Fredrik,
>
> > Many thanks for your prompt review, Maciej!
>
> Maciej, I am equally grateful for you stepping in to get Fredrik's
> contribution reviewed.  I have taken a look through and have no
> additional comments.  I'm going to be travelling this weekend so
> I'd like to ask Maciej to take a quick look at the v2 version but
> otherwise pre-approve it.
>
> Has your copyright assignment come through for GCC? I can't access
> the copyright info at the moment to check myself. Obviously that will
> be a blocker otherwise.
>
> I hope you do manage to work through other r5900 issues and if so the
> changes will be most welcome.
>
> Thanks,
> Matthew


      parent reply	other threads:[~2018-12-16 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3124fcb08e433bc230f53fae9d0e7bd6998f8538.1541607095.git.noring@nocrew.org>
     [not found] ` <alpine.LFD.2.21.1811082217010.7359@eddie.linux-mips.org>
     [not found]   ` <20181109184319.GA18544@sx9>
     [not found]     ` <00ed01d4787b$caae0620$600a1260$@gmail.com>
2018-12-16 20:33       ` Christopher Faylor
2018-12-16 20:38       ` Christopher Faylor [this message]

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=CALOBT3CZWJMnjhWoQL7A_-7S6BqF5jFHQC82txBg0RhmOQFn9w@mail.gmail.com \
    --to=cgf000@gmail.com \
    --cc=JuergenUrban@cgf.cx \
    --cc=gcc-patches@cgf.cx \
    --cc=macro@cgf.cx \
    --cc=noring@cgf.cx \
    --cc=test-list@sourceware.org \
    /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).