From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 0/2] arm64: dts: qcom: sa8775p-ride: support both board variants
Date: Wed, 19 Jun 2024 20:50:23 +0200 [thread overview]
Message-ID: <4df2a52c-c21e-4da0-9ca0-13f28e81018c@linaro.org> (raw)
In-Reply-To: <20240619183255.34107-1-brgl@bgdev.pl>
On 6/19/24 20:32, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> Split the current .dts into two: the existing one keeps the name and
> supports revision 2 of the board while patch 2 adds a .dts for revision 3.
Are both gonna be actively used?
Konrad
next prev parent reply other threads:[~2024-06-19 18:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 18:32 [PATCH 0/2] arm64: dts: qcom: sa8775p-ride: support both board variants Bartosz Golaszewski
2024-06-19 18:32 ` [PATCH 1/2] arm64: dts: qcom: move common parts for sa8775p-ride variants into a .dtsi Bartosz Golaszewski
2024-06-19 18:32 ` [PATCH 2/2] arm64: dts: qcom: sa8775p-ride-r3: add new board file Bartosz Golaszewski
2024-06-19 18:53 ` Konrad Dybcio
2024-06-20 1:27 ` kernel test robot
2024-06-20 16:03 ` Andrew Halaney
2024-06-21 13:14 ` Bartosz Golaszewski
2024-06-21 14:54 ` Andrew Halaney
2024-06-19 18:50 ` Konrad Dybcio [this message]
2024-06-20 7:07 ` [PATCH 0/2] arm64: dts: qcom: sa8775p-ride: support both board variants Bartosz Golaszewski
2024-06-20 16:00 ` Andrew Halaney
2024-06-22 11:04 ` 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=4df2a52c-c21e-4da0-9ca0-13f28e81018c@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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;
as well as URLs for NNTP newsgroup(s).