From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rinat Muhamedgaliev <rinat.muhamedgaliev@gmail.com>,
linux-pm@vger.kernel.org
Cc: "Sebastian Reichel" <sre@kernel.org>,
"Pali Rohár" <pali@kernel.org>, "Andrew F . Davis" <afd@ti.com>,
"Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com>,
"David Heidelberg" <david@ixit.cz>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8] bq27xxx: support interchangeable OnePlus 6/6T fuel gauges
Date: Tue, 3 Nov 2026 21:47:03 +0100 [thread overview]
Message-ID: <b6fccb70-596b-4b60-9086-04223a77e395@kernel.org> (raw)
In-Reply-To: <20261103204129.278715-1-rinat.muhamedgaliev@gmail.com>
On 03/11/2026 21:41, Rinat Muhamedgaliev wrote:
> Hi,
>
> Gentle ping on this series. v8 moves the DeviceType check to the
> bus-neutral core and uses the existing register access helpers, as
> suggested in the review.
>
> Please let me know if any further changes or testing are needed.
>
You sent it right on start of merge window and you ping 2 days after
merge window finished. How do you exactly imagine this being handled
(yes, I know some maintainers take patches during merge window, but that
is exception)? Please relax, be sure you addressed entire feedback,
before needless pinging around standard quiet periods.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-11-03 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 19:08 Rinat Muhamedgaliev via B4 Relay
2026-10-19 19:08 ` [PATCH v8] power: supply: bq27xxx: detect bq27541 behind bq27411 compatible Rinat Muhamedgaliev via B4 Relay
2026-11-03 20:41 ` [PATCH v8] bq27xxx: support interchangeable OnePlus 6/6T fuel gauges Rinat Muhamedgaliev
2026-11-03 20:47 ` Krzysztof Kozlowski [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=b6fccb70-596b-4b60-9086-04223a77e395@kernel.org \
--to=krzk@kernel.org \
--cc=afd@ti.com \
--cc=david@ixit.cz \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pali@kernel.org \
--cc=rinat.muhamedgaliev@gmail.com \
--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
all inboxes | Powered by JetHome®