All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Faruque Ansari <faruque.ansari@oss.qualcomm.com>,
	kernel@oss.qualcomm.com
Cc: avaneesh.dwivedi@oss.qualcomm.com, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: power: reset: add PSCRR NVMEM recorder binding
Date: Tue, 18 Aug 2026 08:47:48 +0200	[thread overview]
Message-ID: <9d494af0-bd84-46e2-91f7-b59bc6da9b89@kernel.org> (raw)
In-Reply-To: <20260817-pscrr-provider-v1-1-88a318c13d41@oss.qualcomm.com>

On 17/08/2026 15:29, Faruque Ansari wrote:
> Add binding for the PSCRR NVMEM recorder. Records the power state
> change reason into a small NVMEM cell — such as a PMIC SDAM byte or
> RTC scratch register — so the cause survives a power cycle and can be
> read back on the next boot.
> 
> Signed-off-by: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
> ---

Why are you sending emails to kernel@oss mailing list? This is only
internal.

Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.

Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.

You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.

Please kindly resend and include all necessary To/Cc entries.

Please follow writing bindings, writing schema and DTS101 slides before
next submission. I see at least a few trivial issues which should not be
there.

Best regards,
Krzysztof

  reply	other threads:[~2026-08-18  6:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 13:29 [PATCH 0/4] power: reset: add NVMEM recorder provider for PSCRR Faruque Ansari
2026-08-17 13:29 ` [PATCH 1/4] dt-bindings: power: reset: add PSCRR NVMEM recorder binding Faruque Ansari
2026-08-18  6:47   ` Krzysztof Kozlowski [this message]
2026-08-18 10:29     ` Faruque Ansari
2026-08-17 13:29 ` [PATCH 2/4] power: reset: add PSCRR NVMEM recorder Faruque Ansari
2026-08-18  9:02   ` Uwe Kleine-König
2026-08-17 13:29 ` [PATCH 3/4] nvmem: provide consumer access to cell size metrics Faruque Ansari
2026-08-17 13:29 ` [PATCH 4/4] arm64: dts: qcom: lemans: add PSCRR NVMEM recorder node Faruque Ansari

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=9d494af0-bd84-46e2-91f7-b59bc6da9b89@kernel.org \
    --to=krzk@kernel.org \
    --cc=avaneesh.dwivedi@oss.qualcomm.com \
    --cc=faruque.ansari@oss.qualcomm.com \
    --cc=kernel@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.