On 27 October 2016 at 19:04, Paul Burton <paul.bur...@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
