From: Krzysztof Kozlowski <krzk@kernel.org>
To: George Moussalem <george.moussalem@outlook.com>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, amitk@kernel.org,
thara.gopinath@gmail.com, dmitry.baryshkov@linaro.org,
robh@kernel.org, krzk+dt@kernel.org, quic_srichara@quicinc.com
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v4 1/5] dt-bindings: nvmem: Add compatible for IPQ5018
Date: Fri, 21 Feb 2025 09:29:28 +0100 [thread overview]
Message-ID: <4420c389-e53e-4f10-b2f7-7a5429d282ce@kernel.org> (raw)
In-Reply-To: <DS7PR19MB8883C8E61B02269AAD7D8C1C9DC72@DS7PR19MB8883.namprd19.prod.outlook.com>
On 21/02/2025 07:52, George Moussalem wrote:
> From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
>
> Document the QFPROM block found on IPQ5018
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Sricharan Ramabadhran <quic_srichara@quicinc.com>
> Signed-off-by: George Moussalem <george.moussalem@outlook.com>
Any explanation why you are sending this? Why there is no cover letter?
This is 1.5 year old work, so I assume Qualcomm is abandoning this chip
and maybe there is no point in merging this in the first place?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-21 8:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250221065219.17036-1-george.moussalem@outlook.com>
2025-02-21 6:52 ` [PATCH v4 1/5] dt-bindings: nvmem: Add compatible for IPQ5018 George Moussalem
2025-02-21 8:29 ` Krzysztof Kozlowski [this message]
2025-02-21 10:08 ` George Moussalem
2025-02-21 10:49 ` Krzysztof Kozlowski
2025-02-21 10:06 ` George Moussalem
2025-02-21 6:52 ` [PATCH v4 2/5] dt-bindings: thermal: qcom-tsens: Add ipq5018 compatible George Moussalem
2025-02-21 6:52 ` [PATCH v4 3/5] thermal: drivers: qcom: Add new feat for soc without rpm George Moussalem
2025-02-21 6:52 ` [PATCH v4 4/5] thermal: qcom: tsens: Add support for IPQ5018 tsens George Moussalem
2025-02-21 13:59 ` Dmitry Baryshkov
2025-02-21 14:13 ` George Moussalem
2025-02-21 14:29 ` Dmitry Baryshkov
2025-02-21 14:41 ` George Moussalem
2025-02-21 14:51 ` Dmitry Baryshkov
2025-02-24 5:43 ` Sricharan Ramabadhran
2025-02-21 6:52 ` [PATCH v4 5/5] arm64: dts: qcom: ipq5018: Add tsens node George Moussalem
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=4420c389-e53e-4f10-b2f7-7a5429d282ce@kernel.org \
--to=krzk@kernel.org \
--cc=amitk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=george.moussalem@outlook.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_srichara@quicinc.com \
--cc=robh@kernel.org \
--cc=thara.gopinath@gmail.com \
/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