From: Krzysztof Kozlowski <krzk@kernel.org>
To: Hrishabh Rajput <hrishabh.rajput@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: Add binding for gunyah watchdog
Date: Thu, 4 Sep 2025 15:17:55 +0200 [thread overview]
Message-ID: <29a91114-d862-452e-b7bf-1b659ad7d831@kernel.org> (raw)
In-Reply-To: <099a7c48-c447-40d4-9076-570f5a5058a2@oss.qualcomm.com>
On 04/09/2025 15:07, Hrishabh Rajput wrote:
>>> +properties:
>>> + compatible:
>>> + allOf:
>>> + - const: gunyah-hypervisor
>>> + - const: simple-bus
>> What? No.
>>
>> Don't create patches with AI.
>
> This patch was not created with AI. Reference was taken from the patch [1].
There is no such syntax like allOf in [1]. Nowhere in Linux kernel, btw,
that's some total invention, thus my gut told me - it must be made with
poor AI tools.
>
> That being said, I see your point about the mistakes which were made
> while adding the compatible "simple-bus".
> I apologize for the same.
>
> I will make sure `make dt_binding_check` passes with latest versions of
> dtschema and yamllint as pointed out by Rob and as should have been done
> with this patch as well.
No, that's not enough.
You should ask for internal review. I did an extra effort, I checked
that and:
1. You did post it for internal review, BUT:
2. Your internal testing system pointed out errors (schema failure) or
failed itself,
3. You did not ask your internal testing system to RETEST the patch, in
case this was a system failure. That's your mistake. If this was true
failure of schema, then you obviously should not send it, but
investigate why schema fails on your patch.
4. You did not receive review (at least no track of it) but decided to
post it on mailing list. That's also your mistake, because lack of
internal review does not mean you can post it to the mailing lists. Talk
with your managers or colleagues about missing review, for example.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-04 13:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 19:33 [PATCH 0/2] Add support for Gunyah Watchdog Hrishabh Rajput via B4 Relay
2025-09-03 19:33 ` [PATCH 1/2] dt-bindings: Add binding for gunyah watchdog Hrishabh Rajput via B4 Relay
2025-09-03 23:27 ` Rob Herring (Arm)
2025-09-04 9:52 ` Krzysztof Kozlowski
2025-09-04 10:16 ` Pavan Kondeti
2025-09-04 10:49 ` Krzysztof Kozlowski
2025-09-04 10:59 ` Krzysztof Kozlowski
2025-09-04 12:29 ` Pavan Kondeti
2025-09-04 13:07 ` Hrishabh Rajput
2025-09-04 13:17 ` Krzysztof Kozlowski [this message]
2025-09-04 19:03 ` Hrishabh Rajput
2025-09-03 19:34 ` [PATCH 2/2] watchdog: Add driver for Gunyah Watchdog Hrishabh Rajput via B4 Relay
2025-09-03 20:13 ` Bjorn Andersson
2025-09-04 11:40 ` Hrishabh Rajput
2025-09-04 13:47 ` Bjorn Andersson
2025-09-04 17:11 ` Pavan Kondeti
2025-09-05 9:19 ` Konrad Dybcio
2025-09-04 0:10 ` [PATCH 0/2] Add support " Rob Herring
2025-09-04 11:31 ` Konrad Dybcio
2025-09-04 22:51 ` Rob Herring
2025-09-05 0:00 ` Pavan Kondeti
2025-09-05 10:18 ` Konrad Dybcio
2025-09-08 5:49 ` Pavan Kondeti
2025-09-12 11:16 ` Konrad Dybcio
2025-09-04 14:39 ` Hrishabh Rajput
2025-09-04 7:13 ` Neil Armstrong
2025-09-04 9:18 ` Pavan Kondeti
2025-09-04 13:53 ` Bjorn Andersson
2025-09-04 17:05 ` Pavan Kondeti
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=29a91114-d862-452e-b7bf-1b659ad7d831@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hrishabh.rajput@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.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=robh@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