From: Conor Dooley <conor.dooley@microchip.com>
To: Walker Chen <walker.chen@starfivetech.com>
Cc: Conor Dooley <conor@kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-pm@vger.kernel.org>,
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] JH7110 PMU Support
Date: Tue, 17 Jan 2023 08:19:22 +0000 [thread overview]
Message-ID: <Y8ZaCpEsmG4hChn+@wendy> (raw)
In-Reply-To: <02174460-87b8-bb1c-7b6f-39694fa416c3@starfivetech.com>
[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]
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@starfivetech.com
> > 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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com>
To: Walker Chen <walker.chen@starfivetech.com>
Cc: Conor Dooley <conor@kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-pm@vger.kernel.org>,
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] JH7110 PMU Support
Date: Tue, 17 Jan 2023 08:19:22 +0000 [thread overview]
Message-ID: <Y8ZaCpEsmG4hChn+@wendy> (raw)
In-Reply-To: <02174460-87b8-bb1c-7b6f-39694fa416c3@starfivetech.com>
[-- Attachment #1.1: Type: text/plain, Size: 2068 bytes --]
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@starfivetech.com
> > 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 #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-01-17 8:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 7:42 [PATCH v3 0/3] JH7110 PMU Support Walker Chen
2023-01-16 7:42 ` Walker Chen
2023-01-16 7:42 ` [PATCH v3 1/3] dt-bindings: power: Add starfive,jh7110-pmu Walker Chen
2023-01-16 7:42 ` Walker Chen
2023-01-17 10:55 ` Krzysztof Kozlowski
2023-01-17 10:55 ` Krzysztof Kozlowski
2023-01-18 7:03 ` Walker Chen
2023-01-18 7:03 ` Walker Chen
2023-01-16 7:42 ` [PATCH v3 2/3] soc: starfive: Add StarFive JH71XX pmu driver Walker Chen
2023-01-16 7:42 ` Walker Chen
2023-01-17 10:09 ` Heiko Stübner
2023-01-17 10:09 ` Heiko Stübner
2023-01-18 6:45 ` Walker Chen
2023-01-18 6:45 ` Walker Chen
2023-01-16 7:42 ` [PATCH v3 3/3] riscv: dts: starfive: add pmu controller node Walker Chen
2023-01-16 7:42 ` Walker Chen
2023-01-16 19:19 ` [PATCH v3 0/3] JH7110 PMU Support Conor Dooley
2023-01-16 19:19 ` Conor Dooley
2023-01-17 7:45 ` Walker Chen
2023-01-17 7:45 ` Walker Chen
2023-01-17 8:19 ` Conor Dooley [this message]
2023-01-17 8:19 ` Conor Dooley
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=Y8ZaCpEsmG4hChn+@wendy \
--to=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=walker.chen@starfivetech.com \
/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.