On Thu, Sep 29, 2022 at 18:59:24 +0100, Conor Dooley wrote: > On Thu, Sep 29, 2022 at 04:45:26PM +0200, Krzysztof Kozlowski wrote: > > On 29/09/2022 16:31, Hal Feng wrote: > > > > > This series is also available at > > > https://github.com/hal-feng/linux/commits/visionfive2-minimal > > > > > > [1] > > > https://www.cnx-software.com/2022/08/23/starfive-visionfive-2-quad-c > > > ore-risc-v-sbc-linux/ > > > [2] https://wiki.rvspace.org/ > > > > > > Emil Renner Berthing (17): > > > dt-bindings: riscv: Add StarFive JH7110 bindings > > > dt-bindings: timer: Add StarFive JH7110 clint > > > dt-bindings: interrupt-controller: Add StarFive JH7110 plic > > > dt-bindings: sifive-l2-cache: Support StarFive JH71x0 SoCs > > > soc: sifive: l2 cache: Convert to platform driver > > > soc: sifive: l2 cache: Add StarFive JH71x0 support > > > reset: starfive: jh7100: Use 32bit I/O on 32bit registers > > > dt-bindings: reset: Add StarFive JH7110 reset definitions > > > clk: starfive: Factor out common clock driver code > > > dt-bindings: clock: Add StarFive JH7110 system clock definitions > > > dt-bindings: clock: Add starfive,jh7110-clkgen-sys bindings > > > clk: starfive: Add StarFive JH7110 system clock driver > > > dt-bindings: clock: Add StarFive JH7110 always-on definitions > > > dt-bindings: clock: Add starfive,jh7110-clkgen-aon bindings > > > clk: starfive: Add StarFive JH7110 always-on clock driver > > > RISC-V: Add initial StarFive JH7110 device tree > > > RISC-V: Add StarFive JH7110 VisionFive2 board device tree > > > > Where is the rest of patches? Lists got only 5 of them. Anyway this is > > a bit too big patchset. Split per subsystem. > > They seem to be coming in over time in dribs and drabs. I assume it is not a > mailing list problem given how many lists are CCed on the mail and the fact > that they have different providers. > > For v2 (or multiple v2s) please fix up your process so that this gets sent > normally and not a couple of patches every hour. Our email server has technical issue and we are aware of this. Will fix in next revision. Sorry for the inconvenience caused. Best Regards, Hal
