public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Sicelo <absicsz@gmail.com>, Sebastian Reichel <sre@kernel.org>,
	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: Thu, 13 Mar 2025 08:42:31 +0100	[thread overview]
Message-ID: <20250313084231.7e132b17@akair> (raw)
In-Reply-To: <FF01728B-C13C-4CD8-8F61-419AACE03C0C@goldelico.com>

Am Thu, 13 Mar 2025 08:28:35 +0100
schrieb "H. Nikolaus Schaller" <hns@goldelico.com>:

> Hi Sicelo,
> please can you append the patch to the e-mail as usual?
> 
That just applies, no issues.
$ b4 shazam https://lore.kernel.org/linux-pm/20250312121712.146109-1-absicsz@gmail.com/T/#t
Grabbing thread from lore.kernel.org/all/20250312121712.146109-1-absicsz%40gmail.com/t.mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
Analyzing 3 messages in the thread
Checking attestation on all messages, may take a moment...
---
  ✓ [PATCH 1/2] Revert "power: supply: bq27xxx: do not report bogus zero values"
  ✓ [PATCH 2/2] power: supply: bq27xxx: do not report incorrect zero values
  ---
  ✓ Signed: DKIM/gmail.com
---
Total patches: 2
---
Applying: Revert "power: supply: bq27xxx: do not report bogus zero values"
Applying: power: supply: bq27xxx: do not report incorrect zero values


> Then "git am" can easily be applied or it can be found in patchwork.
> 
> BR and thanks,
> Nikolaus
[...]
> > 
> > [0] https://lore.kernel.org/linux-pm/20250312121712.146109-1-absicsz@gmail.com/T/#t  
> 
> 
Regards,
Andreas

      reply	other threads:[~2025-03-13  7:42 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
2025-03-12 12:28             ` Sicelo
2025-03-13  7:28               ` H. Nikolaus Schaller
2025-03-13  7:42                 ` Andreas Kemnade [this message]

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=20250313084231.7e132b17@akair \
    --to=andreas@kemnade.info \
    --cc=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