From: Andreas Kemnade <andreas@kemnade.info>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Sebastian Reichel" <sre@kernel.org>,
"Jerry Lv" <Jerry.Lv@axis.com>, "Pali Rohár" <pali@kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
letux-kernel@openphoenux.org, stable@vger.kernel.org,
kernel@pyra-handheld.com
Subject: Re: [PATCH v2 0/2] power: supply: bq27xxx: bug fixes
Date: Thu, 28 Aug 2025 20:24:21 +0200 [thread overview]
Message-ID: <20250828202421.57bbbd2c@akair> (raw)
In-Reply-To: <cover.1755945297.git.hns@goldelico.com>
Am Sat, 23 Aug 2025 12:34:55 +0200
schrieb "H. Nikolaus Schaller" <hns@goldelico.com>:
> PATCH V2 2025-08-23 12:33:18:
> Changes:
> * improved commit description of main fix
> * new patch: adds a restriction of historical no-battery-detection logic to the bq27000 chip
>
> PATCH V1 2025-07-21 14:46:09:
>
>
> H. Nikolaus Schaller (2):
> power: supply: bq27xxx: fix error return in case of no bq27000 hdq
> battery
> power: supply: bq27xxx: restrict no-battery detection to bq27000
>
hmm, is the order correct? To me to be bisectable, should it be turned
around? Maybe Sebastian just can do that while picking it.
Regards,
Andreas
next prev parent reply other threads:[~2025-08-28 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 10:34 [PATCH v2 0/2] power: supply: bq27xxx: bug fixes H. Nikolaus Schaller
2025-08-23 10:34 ` [PATCH v2 1/2] power: supply: bq27xxx: fix error return in case of no bq27000 hdq battery H. Nikolaus Schaller
2025-08-23 14:46 ` Markus Elfring
2025-08-23 14:54 ` Greg KH
2025-08-23 10:34 ` [PATCH v2 2/2] power: supply: bq27xxx: restrict no-battery detection to bq27000 H. Nikolaus Schaller
2025-08-28 7:33 ` Jerry Lv
2025-08-28 11:45 ` [Letux-kernel] " H. Nikolaus Schaller
2025-08-28 18:24 ` Andreas Kemnade [this message]
2025-08-28 20:11 ` [PATCH v2 0/2] power: supply: bq27xxx: bug fixes H. Nikolaus Schaller
2025-09-06 0:32 ` 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=20250828202421.57bbbd2c@akair \
--to=andreas@kemnade.info \
--cc=Jerry.Lv@axis.com \
--cc=hns@goldelico.com \
--cc=kernel@pyra-handheld.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pali@kernel.org \
--cc=sre@kernel.org \
--cc=stable@vger.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 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.