From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kathiravan T <quic_kathirav@quicinc.com>,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, wim@linux-watchdog.org,
linux@roeck-us.net, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/2] dt-bindings: watchdog: qcom-wdt: add qcom,apss-wdt-ipq5332 compatible
Date: Sun, 16 Apr 2023 12:19:15 +0200 [thread overview]
Message-ID: <1613da77-d77e-94c6-802a-b2d856c5b40f@linaro.org> (raw)
In-Reply-To: <0569ed09-2241-d981-4e0c-209caa7483ab@quicinc.com>
On 13/04/2023 06:39, Kathiravan T wrote:
>
> On 3/20/2023 4:15 PM, Kathiravan T wrote:
>> Add a compatible for the IPQ5332 platform's APSS watchdog.
>
> Guenter,
>
>
> Without this patch, I see dtbs_check failure in linux-next.
>
>
> I see you reviewed the V1 of this patch, can you pick up this patch? I don't see it in https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git/log/?h=watchdog-next
> I'm not sure if I am looking at the right tree, Please correct me if I am wrong.
Are you sure that patch still applies?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-04-16 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 10:45 [PATCH V2 0/2] Add few device nodes for IPQ5332 SoC Kathiravan T
2023-03-20 10:45 ` [PATCH V2 1/2] dt-bindings: watchdog: qcom-wdt: add qcom,apss-wdt-ipq5332 compatible Kathiravan T
2023-04-13 4:39 ` Kathiravan T
2023-04-16 10:19 ` Krzysztof Kozlowski [this message]
2023-04-16 15:43 ` Guenter Roeck
2023-03-20 10:45 ` [PATCH V2 2/2] arm64: dts: qcom: ipq5332: add few device nodes Kathiravan T
2023-03-30 15:30 ` [PATCH V2 0/2] Add few device nodes for IPQ5332 SoC Kathiravan T
2023-04-07 17:41 ` (subset) " Bjorn Andersson
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=1613da77-d77e-94c6-802a-b2d856c5b40f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=quic_kathirav@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.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;
as well as URLs for NNTP newsgroup(s).