devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ChiYuan Huang <cy_huang@richtek.com>
To: Sebastian Reichel <sre@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	<devicetree@vger.kernel.org>, <linux-pm@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND v2 0/3] Add Richtek RT9756 Smart-Cap divider charger
Date: Wed, 17 Sep 2025 10:19:44 +0800	[thread overview]
Message-ID: <aMoawDH7V/ea4i62@git-send.richtek.com> (raw)
In-Reply-To: <aLY3/dNLdF/Iiwq6@git-send.richtek.com>

On Tue, Sep 02, 2025 at 08:19:09AM +0800, ChiYuan Huang wrote:
> On Thu, Aug 14, 2025 at 03:31:05PM +0800, cy_huang@richtek.com wrote:
> > From: ChiYuan Huang <cy_huang@richtek.com>
> > 
> > This patch series adds support for RT9756 charger.
> > 
> > RESEND V2
> > - Add 'Reviewed-by' tag in dt-binding patch
> > 
> > V2
> > - Add reference to 'power-supply.yaml'
> > - Remove 'wakeup-source' from required property list
> > - Use 'unevaluatedProperties' to replace 'additionalProperties'
> 
> Ping......
> It's been one month not receive any patch review comment.
> 
Ping again.
> Regards,
> ChiYuan.

      reply	other threads:[~2025-09-17  2:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14  7:31 [PATCH RESEND v2 0/3] Add Richtek RT9756 Smart-Cap divider charger cy_huang
2025-08-14  7:31 ` [PATCH RESEND v2 1/3] dt-bindings: power: supply: Add Richtek RT9756 smart cap " cy_huang
2025-08-14  7:31 ` [PATCH RESEND v2 2/3] power: supply: rt9756: " cy_huang
2025-09-18 23:43   ` Sebastian Reichel
2025-09-19  8:27     ` ChiYuan Huang
2025-08-14  7:31 ` [PATCH RESEND v2 3/3] Documentation: power: rt9756: Document exported sysfs entries cy_huang
2025-09-02  0:19 ` [PATCH RESEND v2 0/3] Add Richtek RT9756 Smart-Cap divider charger ChiYuan Huang
2025-09-17  2:19   ` ChiYuan Huang [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=aMoawDH7V/ea4i62@git-send.richtek.com \
    --to=cy_huang@richtek.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sre@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;
as well as URLs for NNTP newsgroup(s).