All of lore.kernel.org
 help / color / mirror / Atom feed
From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Conor Dooley <conor@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Walker Chen <walker.chen@starfivetech.com>,
	Hal Feng <hal.feng@starfivetech.com>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/4] dt-bindings: power: Add power-domain header for JH7110
Date: Sat, 20 May 2023 19:10:49 +0800	[thread overview]
Message-ID: <24b0e9bf-7e15-ed9c-5265-3a150e7d3450@starfivetech.com> (raw)
In-Reply-To: <20230519-irk-dwelled-6a499c482e62@spud>



On 2023/5/20 2:42, Conor Dooley wrote:
> On Thu, May 18, 2023 at 11:01:59PM -0700, Changhuang Liang wrote:
>> Add power-domain header for JH7110 SoC, it can use to operate dphy
>> power.
> 
> That is not an accurate description of what you are doing here!
> **IF** you resubmit for another reason, please change that wording
> to match what you are doing here. Otherwise, I will fix it up on
> application.
> 

OK, thanks for your comment


  reply	other threads:[~2023-05-20 11:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19  6:01 [PATCH v4 0/4] Add JH7110 AON PMU support Changhuang Liang
2023-05-19  6:01 ` [PATCH v4 1/4] dt-bindings: power: Add power-domain header for JH7110 Changhuang Liang
2023-05-19 18:42   ` Conor Dooley
2023-05-20 11:10     ` Changhuang Liang [this message]
2023-05-19  6:02 ` [PATCH v4 2/4] soc: starfive: Replace SOC_STARFIVE with ARCH_STARFIVE Changhuang Liang
2023-05-19  6:02 ` [PATCH v4 3/4] soc: starfive: Extract JH7110 pmu private operations Changhuang Liang
2023-05-19  6:02 ` [PATCH v4 4/4] soc: starfive: Add JH7110 AON PMU support Changhuang Liang
2023-07-20  3:46 ` [PATCH v4 0/4] " Changhuang Liang
2023-07-20  6:48   ` Conor Dooley
2023-07-20 17:12 ` Conor Dooley
2023-07-21  3:01   ` Changhuang Liang

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=24b0e9bf-7e15-ed9c-5265-3a150e7d3450@starfivetech.com \
    --to=changhuang.liang@starfivetech.com \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hal.feng@starfivetech.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.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.