Hey Walker, On Tue, Jan 17, 2023 at 03:45:22PM +0800, Walker Chen wrote: > On 2023/1/17 3:19, Conor Dooley wrote: > > It's helpful to do this, as when I went to apply your patch, there were > > some conflicts that needed to be sorted out. Because of your prerequisite > > patches, the usual `b4` commands would not usable. E.g. > > > > b4 am -3 20230116074259.22874-1-walker.chen@xxxxxxxxxxxxxxxx > > Analyzing 4 messages in the thread > > Checking attestation on all messages, may take a moment... > > --- > > [PATCH v3 1/3] dt-bindings: power: Add starfive,jh7110-pmu > > [PATCH v3 2/3] soc: starfive: Add StarFive JH71XX pmu driver > > [PATCH v3 3/3] riscv: dts: starfive: add pmu controller node > > --- > > Total patches: 3 > > Preparing fake-am for v3: JH7110 PMU Support > > ERROR: Could not find matching blob for MAINTAINERS (85e8f83161d7) > > If you know on which tree this patchset is based, > > add it as a remote and perform "git remote update" > > in order to fetch the missing objects. > > > > Fortunately, this is just a driver addition so despite `b4` not > > helping it was easy to resolve but for other patches in the future, > > this may not be the case. > > > > Assuming the dt maintainers are happy with the binding, ping me in 2 > > weeks if no-one else has commented and I'll apply patches 1 & 2. > > Could I drop patch 3 and rebase patch 1 & 2 on the latest mainline then submit as v4 ? I dunno, if someone has the pre-requisites then they should be okay, but I need to apply 1 & 2 without the pre-requisites. I dropped patch 3 & did the rebase myself so that the build bots would be able to build the patches: https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/log/?h=riscv-jh7110_pmu I got the build success email this morning, so they appear happy with it. I would wait for some comments from the dt maintainers on patch 1 before considering re-sending the series. If they have comments, then please do rebase on v6.2 Thanks, Conor.
Attachment:
signature.asc
Description: PGP signature
