From: Sebastian Reichel <sre@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: [GIT PULL] power-supply changes for 6.3 (part 2)
Date: Sat, 4 Mar 2023 01:12:08 +0100 [thread overview]
Message-ID: <cfde34bf-c229-4a5d-b2c4-b76b5ba55dfb@mercury.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]
Hi Linus,
I have some more patches for the v6.3 cycle. They have been in
linux-next for a week without any issues. Please find the details
below.
The following changes since commit c142872ea40a99258e2a86bf5c471bcc81752f56:
power: reset: odroid-go-ultra: fix I2C dependency (2023-02-15 23:49:40 +0100)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git tags/for-v6.3-part2
for you to fetch changes up to 13af134bdc6a9dacec4687e57b2ea8d3e08ff04f:
dt-bindings: power: supply: Revise Richtek RT9467 compatible name (2023-02-25 01:17:24 +0100)
----------------------------------------------------------------
power supply changes for the v6.3 series (part 2)
- Fix DT binding for Richtek RT9467
- Fix a NULL pointer check in the power-supply core
- Document meaning of absent "present" property
----------------------------------------------------------------
Bastien Nocera (1):
ABI: testing: sysfs-class-power: Document absence of "present" property
ChiaEn Wu (1):
dt-bindings: power: supply: Revise Richtek RT9467 compatible name
qinyu (1):
power: supply: fix null pointer check order in __power_supply_register
Documentation/ABI/testing/sysfs-class-power | 3 ++-
.../supply/{richtek,rt9467-charger.yaml => richtek,rt9467.yaml} | 6 +++---
drivers/power/supply/power_supply_core.c | 6 +++---
3 files changed, 8 insertions(+), 7 deletions(-)
rename Documentation/devicetree/bindings/power/supply/{richtek,rt9467-charger.yaml => richtek,rt9467.yaml} (92%)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-03-04 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 0:12 Sebastian Reichel [this message]
2023-03-04 0:39 ` pr-tracker-bot
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=cfde34bf-c229-4a5d-b2c4-b76b5ba55dfb@mercury.local \
--to=sre@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®