From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>, david@ixit.cz
Cc: 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>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Documentation: dt-bindings: arm: qcom: Add Pixel 3 and 3 XL
Date: Mon, 6 Oct 2025 10:09:58 +0200 [thread overview]
Message-ID: <6807638b-b212-44b9-b7cb-e53e1f11c0d9@oss.qualcomm.com> (raw)
In-Reply-To: <bq3jeaxksk33ntdk32ojsdyh2d3qkglvgj6segtc3acizlkrhm@fvdsccdbuook>
On 10/6/25 12:21 AM, Dmitry Baryshkov wrote:
> On Sun, Oct 05, 2025 at 03:16:28PM +0200, David Heidelberg via B4 Relay wrote:
>> From: David Heidelberg <david@ixit.cz>
>>
>> Document the bindings for the Pixel 3 and 3 XL.
>>
>> Signed-off-by: David Heidelberg <david@ixit.cz>
>> ---
>> Documentation/devicetree/bindings/arm/qcom.yaml | 5 ++---
>> 1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
>> index ae43b35565808..2190c5b409748 100644
>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>> @@ -976,9 +976,8 @@ properties:
>>
>> - items:
>> - enum:
>> - - google,cheza
>> - - google,cheza-rev1
>> - - google,cheza-rev2
>
> Why are you removing those?
I removed these a long time ago, the base for this series is 6.17-release
instead of -next :/
Konrad
>
>> + - google,blueline
>> + - google,crosshatch
>> - lenovo,yoga-c630
>> - lg,judyln
>> - lg,judyp
>>
>> --
>> 2.51.0
>>
>>
>
next prev parent reply other threads:[~2025-10-06 8:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-05 13:16 [PATCH 0/2] Add support for Pixel 3 and Pixel 3 XL David Heidelberg via B4 Relay
2025-10-05 13:16 ` [PATCH 1/2] Documentation: dt-bindings: arm: qcom: Add Pixel 3 and " David Heidelberg via B4 Relay
2025-10-05 22:21 ` Dmitry Baryshkov
2025-10-06 8:09 ` Konrad Dybcio [this message]
2025-10-06 10:09 ` David Heidelberg
2025-10-06 10:16 ` Konrad Dybcio
2025-10-06 10:17 ` Dmitry Baryshkov
2025-10-05 13:16 ` [PATCH 2/2] arm64: dts: qcom: Add support for Pixel 3 and Pixel " David Heidelberg via B4 Relay
2025-10-05 13:25 ` David Heidelberg
2025-10-05 22:03 ` Dmitry Baryshkov
2025-10-09 21:20 ` David Heidelberg
2025-10-09 21:50 ` Dmitry Baryshkov
2025-10-10 7:51 ` David Heidelberg
2025-10-10 8:17 ` Dmitry Baryshkov
2025-10-17 16:59 ` David Heidelberg
2025-10-19 11:51 ` Dmitry Baryshkov
2025-10-19 13:02 ` David Heidelberg
2025-10-19 14:53 ` Dmitry Baryshkov
2025-10-17 22:23 ` David Heidelberg
2025-10-19 11:51 ` Dmitry Baryshkov
2025-10-06 12:41 ` Konrad Dybcio
2025-10-17 23:32 ` David Heidelberg
2025-10-05 22:15 ` [PATCH 0/2] " Dmitry Baryshkov
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=6807638b-b212-44b9-b7cb-e53e1f11c0d9@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@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=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