From: Krzysztof Kozlowski <krzk@kernel.org>
To: david@ixit.cz, Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: phodina@protonmail.com, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Documentation: dt-bindings: arm: qcom: Add Pixel 3 and 3 XL
Date: Thu, 30 Oct 2025 08:39:33 +0100 [thread overview]
Message-ID: <f0f3485a-b500-418d-b24e-80d70248d378@kernel.org> (raw)
In-Reply-To: <20251030-pixel-3-v2-1-8caddbe072c9@ixit.cz>
On 30/10/2025 08:24, David Heidelberg via B4 Relay wrote:
> From: David Heidelberg <david@ixit.cz>
>
> Document the bindings for the Pixel 3 and 3 XL.
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-30 7:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 7:24 [PATCH v2 0/2] Add support for Pixel 3 and Pixel 3 XL David Heidelberg via B4 Relay
2025-10-30 7:24 ` [PATCH v2 1/2] Documentation: dt-bindings: arm: qcom: Add Pixel 3 and " David Heidelberg via B4 Relay
2025-10-30 7:39 ` Krzysztof Kozlowski [this message]
2025-10-30 7:24 ` [PATCH v2 2/2] arm64: dts: qcom: Add support for Pixel 3 and Pixel " David Heidelberg via B4 Relay
2025-10-30 11:32 ` Konrad Dybcio
2025-10-30 12:03 ` David Heidelberg
2025-10-30 12:10 ` Konrad Dybcio
2025-11-17 18:35 ` David Heidelberg
2025-11-18 9:31 ` Konrad Dybcio
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=f0f3485a-b500-418d-b24e-80d70248d378@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phodina@protonmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox