From: Jakob Hauser <jahau@rocketmail.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: Lee Jones <lee@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Yang Yingliang <yangyingliang@huawei.com>,
Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
Stephan Gerhold <stephan@gerhold.net>,
Raymond Hackley <raymondhackley@protonmail.com>,
Henrik Grimler <henrik@grimler.se>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Jakob Hauser <jahau@rocketmail.com>
Subject: [PATCH v2 0/3] Remaining patches for RT5033 charger
Date: Sun, 1 Oct 2023 15:17:41 +0200 [thread overview]
Message-ID: <cover.1696165240.git.jahau@rocketmail.com> (raw)
In-Reply-To: cover.1696165240.git.jahau.ref@rocketmail.com
This series adds the missing patch "Add cable detection and USB OTG supply"
to the RT5033 charger driver. The patch didn't make it with the initial
series [1].
In the meantime, two fixes patches [2][3] were squashed into that patch.
Additionally there are two clean-up patches, which are patches No. 2 & 3
in this series.
On squashing the fixes patches into the main patch: I didn't add a
Co-developed-by tag of Stephen because the one fix on the includes seemed
to me below the threshold for that tag.
Changes in v2:
- Patch 1: Squashed fixes patches into patch 1.
- Patch 1: Added Co-developed-by tag of Yang Yingliang and a short
description about that in the commit message.
- Patch 1: Removed Acked-by tag of Sebastian as the patch has changed.
v1: https://lore.kernel.org/linux-pm/cover.1695844349.git.jahau@rocketmail.com/T/#t
[1] https://lore.kernel.org/linux-pm/cover.1684182964.git.jahau@rocketmail.com/T/#t
[2] https://lore.kernel.org/linux-next/20230821125741.3a2474d7@canb.auug.org.au
[3] https://lore.kernel.org/linux-pm/20230822030207.644738-1-yangyingliang@huawei.com/T/#u
Jakob Hauser (3):
power: supply: rt5033_charger: Add cable detection and USB OTG supply
power: supply: rt5033_charger: Simplify initialization of
rt5033_charger_data
power: supply: rt5033_charger: Replace "&pdev->dev" by "charger->dev"
in probe
drivers/power/supply/rt5033_charger.c | 320 ++++++++++++++++++++++++--
1 file changed, 299 insertions(+), 21 deletions(-)
--
2.39.2
next parent reply other threads:[~2023-10-01 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1696165240.git.jahau.ref@rocketmail.com>
2023-10-01 13:17 ` Jakob Hauser [this message]
2023-10-01 13:17 ` [PATCH v2 1/3] power: supply: rt5033_charger: Add cable detection and USB OTG supply Jakob Hauser
2023-10-01 13:17 ` [PATCH v2 2/3] power: supply: rt5033_charger: Simplify initialization of rt5033_charger_data Jakob Hauser
2023-10-01 13:17 ` [PATCH v2 3/3] power: supply: rt5033_charger: Replace "&pdev->dev" by "charger->dev" in probe Jakob Hauser
2023-10-04 22:15 ` [PATCH v2 0/3] Remaining patches for RT5033 charger Sebastian Reichel
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=cover.1696165240.git.jahau@rocketmail.com \
--to=jahau@rocketmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=henrik@grimler.se \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=raymondhackley@protonmail.com \
--cc=sfr@canb.auug.org.au \
--cc=sre@kernel.org \
--cc=stephan@gerhold.net \
--cc=yangyingliang@huawei.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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.