Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney.cavm@gmail.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Ralf <ralf@linux-mips.org>,
	linux-mips <linux-mips@linux-mips.org>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	"Markos (GMail)" <markos.chandras@gmail.com>,
	Markos <markos.chandras@imgtec.com>,
	Paul <paul.burton@imgtec.com>,
	Rob Kendrick <rob.kendrick@codethink.co.uk>,
	Alex Smith <alex@alex-smith.me.uk>,
	Huacai Chen <chenhc@lemote.com>
Subject: Re: Please add my temporary MIPS fixes branch to linux-next
Date: Wed, 30 Jul 2014 10:06:01 -0700	[thread overview]
Message-ID: <53D925F9.5090001@gmail.com> (raw)
In-Reply-To: <53D9169D.3020705@imgtec.com>

On 07/30/2014 09:00 AM, James Hogan wrote:
[...]

> ... Since Ralf appears to be unavailable at the moment ...
>
[...]

This doesn't seem to be a temporary situation.

If we want to keep the MIPS architecture in a functioning state, it may 
make sense to establish an alternate path for merging MIPS patches upstream.

David Daney.

  reply	other threads:[~2014-07-30 17:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 16:00 Please add my temporary MIPS fixes branch to linux-next James Hogan
2014-07-30 17:06 ` David Daney [this message]
2014-07-30 18:17 ` Alex Smith
2014-07-31  8:25   ` James Hogan
2014-07-30 23:06 ` Stephen Rothwell
2014-08-11 11:09 ` James Hogan
2014-08-23 20:24   ` Aaro Koskinen
2014-08-26  9:45     ` Markos Chandras
2014-08-26  9:51       ` James Hogan
2014-08-26  9:55         ` Markos Chandras

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=53D925F9.5090001@gmail.com \
    --to=ddaney.cavm@gmail.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=alex@alex-smith.me.uk \
    --cc=aurelien@aurel32.net \
    --cc=chenhc@lemote.com \
    --cc=james.hogan@imgtec.com \
    --cc=linux-mips@linux-mips.org \
    --cc=markos.chandras@gmail.com \
    --cc=markos.chandras@imgtec.com \
    --cc=paul.burton@imgtec.com \
    --cc=ralf@linux-mips.org \
    --cc=rob.kendrick@codethink.co.uk \
    --cc=sfr@canb.auug.org.au \
    /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