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: Wed, 12 Mar 2025 14:20:41 +0200 [thread overview]
Message-ID: <Z9F8GS9DQHVEqT_j@tp440p.steeds.sam> (raw)
In-Reply-To: <b6xa7az5ohopf52ykp3quomkqpo5xmt2fratcmcw3efmkpa6nm@eth4wv4wm577>
Hi
On Wed, Mar 12, 2025 at 08:19:44AM +0100, Sebastian Reichel wrote:
> Sorry for the delayed response. You need to prepare a follow-up
> patch against power-supply's for-next branch. Dropping the broken
> patch would require rebasing the whole branch. The only options
> you have are:
>
> 1. Revert the original broken patch with a proper long description,
> then create a new fix
> 2. Add a fix on top of the broken fix
>
> Please don't forget to add
>
> Fixes: f3974aca381e ("power: supply: bq27xxx: do not report bogus zero values")
Thank you for the guidance. I have taken option 1 in the new patch [0]
Regards
Sicelo
[0] https://lore.kernel.org/linux-pm/20250312121712.146109-1-absicsz@gmail.com/T/#t
next prev parent reply other threads:[~2025-03-12 12:20 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
2025-03-12 7:19 ` Sebastian Reichel
2025-03-12 12:20 ` Sicelo [this message]
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=Z9F8GS9DQHVEqT_j@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