mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Sebastian Reichel <sre@kernel.org>, Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	 Svyatoslav Ryhel <clamor95@gmail.com>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] power: supply: cpcap-battery: pass static battery cell data from device tree
Date: Tue, 03 Mar 2026 00:51:16 +0100	[thread overview]
Message-ID: <177249547653.612663.3021830485437919831.b4-ty@collabora.com> (raw)
In-Reply-To: <20260130134021.353688-1-clamor95@gmail.com>


On Fri, 30 Jan 2026 15:40:19 +0200, Svyatoslav Ryhel wrote:
> Add an option to populate battery cell properties from the device tree if
> the driver cannot access the battery's NVMEM.
> 
> Svyatoslav Ryhel (2):
>   dt-bindings: power: supply: cpcap-battery: document monitored-battery
>     property
>   power: supply: cpcap-battery: pass static battery cell data from
>     device tree
> 
> [...]

Applied, thanks!

[1/2] dt-bindings: power: supply: cpcap-battery: document monitored-battery property
      commit: 62c395fa887c38dad878741b7a1095ef441ba813
[2/2] power: supply: cpcap-battery: pass static battery cell data from device tree
      commit: ca2199cb7ae0375071609460470eadbbde8a4dd5

Best regards,
-- 
Sebastian Reichel <sebastian.reichel@collabora.com>


      parent reply	other threads:[~2026-03-02 23:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30 13:40 Svyatoslav Ryhel
2026-01-30 13:40 ` [PATCH v1 1/2] dt-bindings: power: supply: cpcap-battery: document monitored-battery property Svyatoslav Ryhel
2026-02-09 17:57   ` Rob Herring (Arm)
2026-01-30 13:40 ` [PATCH v1 2/2] power: supply: cpcap-battery: pass static battery cell data from device tree Svyatoslav Ryhel
2026-02-06  4:24   ` Tony Lindgren
2026-03-02  7:44 ` [PATCH v1 0/2] " Svyatoslav Ryhel
2026-03-02 23:51 ` Sebastian Reichel [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=177249547653.612663.3021830485437919831.b4-ty@collabora.com \
    --to=sebastian.reichel@collabora.com \
    --cc=clamor95@gmail.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 \
    --cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®