linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 0/5] Remaining patches for RT5033 charger
Date: Wed, 27 Sep 2023 22:25:57 +0200	[thread overview]
Message-ID: <cover.1695844349.git.jahau@rocketmail.com> (raw)
In-Reply-To: cover.1695844349.git.jahau.ref@rocketmail.com

This series collects remaining patches for the RT5033 charger driver.

The patches are based on 6.6-rc1.

Mailing list links where the patches were taken from:
 - Patch 1
   https://lore.kernel.org/linux-next/20230821125741.3a2474d7@canb.auug.org.au
 - Patch 2
   https://lore.kernel.org/linux-pm/cover.1684182964.git.jahau@rocketmail.com/T/#m27164a05bbe2ec649be1fc32157b34ba814ff31f
 - Patch 3
   https://lore.kernel.org/linux-pm/20230822030207.644738-1-yangyingliang@huawei.com/T/#u
 - Patches 4 & 5
   https://lore.kernel.org/linux-pm/cover.1686948074.git.jahau@rocketmail.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

Stephen Rothwell (1):
  fixup for "power: Explicitly include correct DT includes"

Yang Yingliang (1):
  power: supply: rt5033_charger: fix missing unlock

 drivers/power/supply/rt5033_charger.c | 320 ++++++++++++++++++++++++--
 1 file changed, 299 insertions(+), 21 deletions(-)

-- 
2.39.2


       reply	other threads:[~2023-09-27 20:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1695844349.git.jahau.ref@rocketmail.com>
2023-09-27 20:25 ` Jakob Hauser [this message]
2023-09-27 20:25   ` [PATCH 1/5] fixup for "power: Explicitly include correct DT includes" Jakob Hauser
2023-09-27 20:25   ` [PATCH 2/5] power: supply: rt5033_charger: Add cable detection and USB OTG supply Jakob Hauser
2023-09-28  5:21     ` Marion & Christophe JAILLET
2023-09-27 20:26   ` [PATCH 3/5] power: supply: rt5033_charger: fix missing unlock Jakob Hauser
2023-09-28  5:23     ` Marion & Christophe JAILLET
2023-09-28 19:46       ` Jakob Hauser
2023-09-30 19:45         ` Sebastian Reichel
2023-09-27 20:26   ` [PATCH 4/5] power: supply: rt5033_charger: Simplify initialization of rt5033_charger_data Jakob Hauser
2023-09-27 20:26   ` [PATCH 5/5] power: supply: rt5033_charger: Replace "&pdev->dev" by "charger->dev" in probe Jakob Hauser
2023-10-04 22:15   ` (subset) [PATCH 0/5] 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.1695844349.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 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).