From: Sicelo <absicsz@gmail.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: pali@kernel.org, Sebastian Reichel <sre@kernel.org>,
linux-pm@vger.kernel.org, maemo-leste@lists.dyne.org,
phone-devel@vger.kernel.org,
Discussions about the Letux Kernel <letux-kernel@openphoenux.org>,
akemnade@kernel.org
Subject: Re: [PATCH] power: supply: bq27xxx: do not report bogus zero values
Date: Fri, 28 Feb 2025 11:54:02 +0200 [thread overview]
Message-ID: <Z8GHuu8RXkcY8utL@tp440p.steeds.sam> (raw)
In-Reply-To: <C0E0C7EA-7C42-4DE3-9FCA-DAAA7B65B583@goldelico.com>
Hi
On Fri, Feb 28, 2025 at 09:27:29AM +0100, H. Nikolaus Schaller wrote:
> >
> > Will you submit the fix, or I should?
>
> I think the patch has not yet been merged anywhere (but I am not sure), so
> you better can send a v2 of the series.
It is in linux-next [0]. Not sure if that counts? I guess the only option
now is to submit a follow-up fix?
> And, I think I have found another potential issue.
Thanks for the review. I will do more thorough testing over the weekend
and send the patch.
[0] https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/power/supply/bq27xxx_battery.c?h=next-20250228&id=f3974aca381e81c0b1418d8ecc12fa62e1e9d31f
Sincerely
Sicelo A. Mhlongo
next prev parent reply other threads:[~2025-02-28 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 21:51 [PATCH] power: supply: bq27xxx: do not report bogus zero values Sicelo A. Mhlongo
2025-02-27 17:14 ` H. Nikolaus Schaller
2025-02-27 17:48 ` H. Nikolaus Schaller
2025-02-28 8:02 ` Sicelo
2025-02-28 8:27 ` H. Nikolaus Schaller
2025-02-28 9:54 ` Sicelo [this message]
2025-02-28 10:01 ` H. Nikolaus Schaller
2025-03-10 17:26 ` Sicelo
2025-03-12 7:19 ` Sebastian Reichel
2025-03-12 12:20 ` Sicelo
2025-03-12 12:28 ` Sicelo
2025-03-13 7:28 ` H. Nikolaus Schaller
2025-03-13 7:42 ` Andreas Kemnade
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=Z8GHuu8RXkcY8utL@tp440p.steeds.sam \
--to=absicsz@gmail.com \
--cc=akemnade@kernel.org \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-pm@vger.kernel.org \
--cc=maemo-leste@lists.dyne.org \
--cc=pali@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=sre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox