From: Ji Sheng Teoh <jisheng.teoh@starfivetech.com>
To: <conor@kernel.org>
Cc: <conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<jisheng.teoh@starfivetech.com>,
<krzysztof.kozlowski+dt@linaro.org>,
<leyfoon.tan@starfivetech.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <mark.rutland@arm.com>,
<peterz@infradead.org>, <robh+dt@kernel.org>,
<tglx@linutronix.de>, <will@kernel.org>
Subject: Re: [PATCH v4 2/2] dt-bindings: perf: starfive: Add JH8100 StarLink PMU
Date: Fri, 17 Nov 2023 08:28:30 +0800 [thread overview]
Message-ID: <20231117002830.1762079-1-jisheng.teoh@starfivetech.com> (raw)
In-Reply-To: <20231116-paycheck-upstairs-8147b6137f7a@squawk>
On Thu, 16 Nov 2023 17:27:17 +0000
Conor Dooley <conor@kernel.org> wrote:
> On Fri, Nov 17, 2023 at 12:23:30AM +0800, Ji Sheng Teoh wrote:
> > Add device tree binding for StarFive's JH8100 StarLink PMU
> > (Performance Monitor Unit).
> >
> > Signed-off-by: Ji Sheng Teoh <jisheng.teoh@starfivetech.com>
>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> Generally, there's no need to submit new versions so quickly - you can
> wait for feedback on multiple patches before resubmitting the entire
> series.
>
> Cheers,
> Conor.
>
Sure, Thanks for reviewing.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-11-17 0:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 16:23 [PATCH v4 0/2] StarFive's StarLink PMU Support Ji Sheng Teoh
2023-11-16 16:23 ` [PATCH v4 1/2] perf: starfive: Add StarLink PMU support Ji Sheng Teoh
2023-11-29 11:02 ` Jonathan Cameron
2023-11-30 8:31 ` Ji Sheng Teoh
2023-12-11 17:54 ` Rob Herring
2023-12-12 1:55 ` Ji Sheng Teoh
2023-11-16 16:23 ` [PATCH v4 2/2] dt-bindings: perf: starfive: Add JH8100 StarLink PMU Ji Sheng Teoh
2023-11-16 17:27 ` Conor Dooley
2023-11-17 0:28 ` Ji Sheng Teoh [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=20231117002830.1762079-1-jisheng.teoh@starfivetech.com \
--to=jisheng.teoh@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peterz@infradead.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox