Linux Power Management development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chris Morgan <macroalpha82@gmail.com>
Cc: linux-pm@vger.kernel.org, linux-rockchip@lists.infradead.org,
	 devicetree@vger.kernel.org, broonie@kernel.org,
	lgirdwood@gmail.com, sre@kernel.org,  heiko@sntech.de,
	conor+dt@kernel.org, krzk+dt@kernel.org, robh@kernel.org,
	 lee@kernel.org, Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH V4 1/5] dt-bindings: mfd: ti,bq25703a: Add TI BQ25703A Charger
Date: Fri, 27 Jun 2025 08:58:42 +0200	[thread overview]
Message-ID: <20250627-lurking-amorphous-elephant-e14c7f@krzk-bin> (raw)
In-Reply-To: <20250626195343.54653-2-macroalpha82@gmail.com>

On Thu, Jun 26, 2025 at 02:53:39PM -0500, Chris Morgan wrote:
> From: Chris Morgan <macromorgan@hotmail.com>
> 
> Document the Texas instruments BQ25703A series of charger managers/
> buck/boost regulators.
> 
> Signed-off-by: Chris Morgan <macromorgan@hotmail.com>

Didn't you receive tag?

> ---
>  .../devicetree/bindings/mfd/ti,bq25703a.yaml  | 117 ++++++++++++++++++
>  1 file changed, 117 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/mfd/ti,bq25703a.yaml

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

<form letter>
This is a friendly reminder during the review process.

It looks like you received a tag and forgot to add it.

If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions of patchset, under or above your Signed-off-by tag, unless
patch changed significantly (e.g. new properties added to the DT
bindings). Tag is "received", when provided in a message replied to you
on the mailing list. Tools like b4 can help here. However, there's no
need to repost patches *only* to add the tags. The upstream maintainer
will do that for tags received on the version they apply.

Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577

If a tag was not added on purpose, please state why and what changed.
</form letter>

Best regards,
Krzysztof


  reply	other threads:[~2025-06-27  6:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26 19:53 [PATCH V4 0/5] Add Texas Instruments BQ25703A Charger Chris Morgan
2025-06-26 19:53 ` [PATCH V4 1/5] dt-bindings: mfd: ti,bq25703a: Add TI " Chris Morgan
2025-06-27  6:58   ` Krzysztof Kozlowski [this message]
2025-06-30 14:33     ` Christopher Morgan
2025-06-30 15:15       ` Diederik de Haas
2025-07-02 20:40       ` Krzysztof Kozlowski
2025-06-26 19:53 ` [PATCH V4 2/5] mfd: bq257xx: Add support for BQ25703A core driver Chris Morgan
2025-06-26 19:53 ` [PATCH V4 3/5] power: supply: bq257xx: Add support for BQ257XX charger Chris Morgan
2025-06-26 19:53 ` [PATCH V4 4/5] regulator: bq257xx: Add bq257xx boost regulator driver Chris Morgan
2025-06-26 19:53 ` [PATCH V4 5/5] arm64: dts: rockchip: Add USB and charger to Gameforce Ace Chris Morgan

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=20250627-lurking-amorphous-elephant-e14c7f@krzk-bin \
    --to=krzk@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=macroalpha82@gmail.com \
    --cc=macromorgan@hotmail.com \
    --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