public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sicelo <absicsz@gmail.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
	pali@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: Mon, 10 Mar 2025 19:26:51 +0200	[thread overview]
Message-ID: <Z88g2yBuRkCl_yAu@tp440p.steeds.sam> (raw)
In-Reply-To: <4D7D3E00-59C6-42F6-AE96-F04970D60E8D@goldelico.com>

Hi Sebastian

On Fri, Feb 28, 2025 at 11:01:35AM +0100, H. Nikolaus Schaller wrote:
> > It is in linux-next [0]. Not sure if that counts?
> 
> Ah, I didn't recognize that (and must admit that I did not search through
> linux-next). Sometimes maintainers close a discussion by telling that it
> has been merged.
> 
> Maybe Sebastian can replace it or recommends a fixup.
> 
> > I guess the only option
> > now is to submit a follow-up fix?

How would you like me to correct the bugs I introduced with the patch in
the subject of this email?

I guess it will either be:

- submit v2 against linux-power-supply/master or
  linux-power-supply/fixes (so the bad commit will be removed from
  future history)
- submit a new patch against linux-power-supply/for-next (so the bad
  commit will always be in the history)
- use a different solution you suggest

I apologize for introducing the bug and have taken the time to more
thoroughly test the changes, with help from HNS. I have the patch ready
now, and just need to be sure how to submit it.

Kind Regards
Sicelo A. Mhlongo

  reply	other threads:[~2025-03-10 17:26 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
2025-02-28 10:01           ` H. Nikolaus Schaller
2025-03-10 17:26             ` Sicelo [this message]
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=Z88g2yBuRkCl_yAu@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