Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-mips@linux-mips.org, ralf@linux-mips.org
Cc: john@phrozen.org, david.daney@cavium.com
Subject: Maintenance of Linux/MIPS?
Date: Fri, 25 Aug 2017 14:21:33 -0700	[thread overview]
Message-ID: <c96eaa42-ab7f-d902-746c-c6cff242c596@gmail.com> (raw)

Hi,

There are a lot of patches at
https://patchwork.linux-mips.org/project/linux-mips/list/ that appear to
be under the "New" state and have not had a chance to be reviewed yet.

What can we do to help speed up the review process, do we need more
reviewers? It seems like most patches affecting Linux/MIPS are still
core MIPS kernel changes, but would it help if say, people were queuing
SoC/board specific patches in trees and submit pull requests? Would that
help lower the amount of patches to review?

Any other suggestion?

Thanks!
-- 
Florian

             reply	other threads:[~2017-08-25 21:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 21:21 Florian Fainelli [this message]
2017-08-25 23:07 ` Maintenance of Linux/MIPS? Paul Burton
2017-08-25 23:07   ` Paul Burton
2017-08-25 23:14   ` David Daney
2017-08-30 10:49     ` Matt Redfearn
2017-08-30 10:49       ` Matt Redfearn
2017-09-02 19:34       ` [PATCH] MAINTAINERS: Add James as MIPS co-maintainer Florian Fainelli

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=c96eaa42-ab7f-d902-746c-c6cff242c596@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=david.daney@cavium.com \
    --cc=john@phrozen.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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