All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Paul Burton <paul.burton@imgtec.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Yongbok Kim <Yongbok.Kim@imgtec.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/8] MIPS Boston board support
Date: Thu, 27 Oct 2016 19:17:35 +0100	[thread overview]
Message-ID: <CAFEAcA-uY1A8vNgjSK89xrKh4fgLZFnxs-sR9g=W-BTjGS7T5w@mail.gmail.com> (raw)
In-Reply-To: <14097837.HPlHJBIeFp@np-p-burton>

On 27 October 2016 at 19:04, Paul Burton <paul.burton@imgtec.com> wrote:
> On Thursday, 8 September 2016 15:51:50 BST Paul Burton wrote:
>> This series introduces support for the MIPS Boston development board. It
>> begins by introducing support for moving MIPS Coherence Manager GCRs which
>> Boston software typically does to avoid conflicting with its flash memory
>> region. An API is then added to retrieve the emulated MIPS GIC timer
>> frequency, which is used to report system clock frequency to software via
>> "platform registers" which the Boston board provides. An issue with the
>> MIPS GIC that current Boston Linux kernels encounter is fixed, and an API
>> introduced to allow the board to determine whether the MIPS CPS hardware is
>> supported.

> Is there anything else I can do to move this along? These patches have been
> sat waiting for review or merging for what's approaching 2 months now.

As a general rule, the way our dev process works is that until a
maintainer actively picks up a patchset it's still "owned" by the
submitter, and so you have to check that it hasn't been forgotten
and send 'ping' emails as necessary (usually after a couple of weeks
of nothing-happening) to ensure it doesn't get lost.

In this case I suspect the patchset may have accidentally got lost
in the transition of MIPS maintainers from Leon to Yongbok.

thanks
-- PMM

      reply	other threads:[~2016-10-27 18:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 14:51 [Qemu-devel] [PATCH v2 0/8] MIPS Boston board support Paul Burton
2016-09-08 14:51 ` [Qemu-devel] [PATCH v2 1/8] hw/mips_cmgcr: allow GCR base to be moved Paul Burton
2016-09-08 14:51 ` [Qemu-devel] [PATCH v2 2/8] hw/mips_gictimer: provide API for retrieving frequency Paul Burton
2016-09-08 14:51 ` [Qemu-devel] [PATCH v2 3/8] hw/mips_gic: Update pin state on mask changes Paul Burton
2016-09-08 14:51 ` [Qemu-devel] [PATCH v2 4/8] target-mips: Provide function to test if a CPU supports an ISA Paul Burton
2016-09-08 14:51 ` [Qemu-devel] [PATCH v2 5/8] dtc: Update requirement to v1.4.2 Paul Burton
2016-09-08 14:51 ` [Qemu-devel] [PATCH v2 6/8] loader: Support Flattened Image Trees (FIT images) Paul Burton
2016-10-27 23:31   ` Yongbok Kim
2016-09-08 14:51 ` [Qemu-devel] [PATCH v2 7/8] hw: xilinx-pcie: Add support for Xilinx AXI PCIe Controller Paul Burton
2016-11-28 23:37   ` Alistair Francis
2016-09-08 14:51 ` [Qemu-devel] [PATCH v2 8/8] hw/mips: MIPS Boston board support Paul Burton
2017-01-24  0:17   ` Yongbok Kim
2016-09-08 18:58 ` [Qemu-devel] [PATCH v2 0/8] " no-reply
2016-09-08 21:16   ` Paul Burton
2016-10-27 18:04 ` Paul Burton
2016-10-27 18:17   ` Peter Maydell [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='CAFEAcA-uY1A8vNgjSK89xrKh4fgLZFnxs-sR9g=W-BTjGS7T5w@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=Yongbok.Kim@imgtec.com \
    --cc=aurelien@aurel32.net \
    --cc=paul.burton@imgtec.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.