From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yijie Yang <yijie.yang@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Srinivas Kandagatla <srini@kernel.org>,
Amol Maheshwari <amahesh@qti.qualcomm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: misc: qcom,fastrpc: Add Maili FastRPC compatible
Date: Mon, 1 Jun 2026 11:59:27 +0200 [thread overview]
Message-ID: <c9aacef4-d10d-4f9f-8bf3-fd53501a1831@kernel.org> (raw)
In-Reply-To: <e00a4089-021b-4c26-8a6e-ba1faf86218f@oss.qualcomm.com>
On 01/06/2026 03:23, Yijie Yang wrote:
>>>
>>> Okay...
>>
>> If a human cannot write and validate this one, I see as putting effort
>> on maintainers.
>>
>> Dropping from patchwork.
>
> I will write and validate this myself and then remove this tag.
Upstream maintainer's task is not to review AI generated code, but
review people's code. I have no clue which case is here and
unfortunately I make assumptions, usually in favor of less work for me.
If contributors send us AI code, then basically contributors are proxies
between the AI model and maintainer. I don't want to talk with your AI
through you, I have no such interests (and such process would not
scale). Reviewing AI code does not give me actual pleasure of work - I
have zero emotional connection to such code, no pleasure, I simply do
not care and decide to spend my time on something else.
Whether you actually use AI is a different thing, just like using other
tools, but if a trivial patch is done with AI, I don't believe it was
reviewed by you, because writing it is a similar amount of effort, so
obvious choice for me would be to write it by myself.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-06-01 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 6:21 [PATCH] dt-bindings: misc: qcom,fastrpc: Add Maili FastRPC compatible Yijie Yang
2026-05-25 8:37 ` Dmitry Baryshkov
2026-05-25 9:37 ` Yijie Yang
2026-05-25 10:08 ` Dmitry Baryshkov
2026-05-30 11:20 ` Krzysztof Kozlowski
2026-06-01 1:23 ` Yijie Yang
2026-06-01 9:59 ` 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=c9aacef4-d10d-4f9f-8bf3-fd53501a1831@kernel.org \
--to=krzk@kernel.org \
--cc=amahesh@qti.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=srini@kernel.org \
--cc=yijie.yang@oss.qualcomm.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