devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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, netdev@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v2 3/3] arm64: dts: qcom: sa8775p-ride-r3: add new board file
Date: Wed, 26 Jun 2024 17:08:38 +0200	[thread overview]
Message-ID: <5d0489e4-d04e-4ade-8fb4-b70ed5099d92@linaro.org> (raw)
In-Reply-To: <20240625151430.34024-4-brgl@bgdev.pl>

On 25.06.2024 5:14 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> 
> Revision 3 of the sa8775p-ride board uses a different PHY for the two
> ethernet ports and supports 2.5G speed. Create a new file for the board
> reflecting the changes.
> 
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---

Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>

Konrad

  reply	other threads:[~2024-06-26 15:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 15:14 [PATCH v2 0/3] arm64: dts: qcom: sa8775p-ride: support both board variants Bartosz Golaszewski
2024-06-25 15:14 ` [PATCH v2 1/3] dt-bindings: arm: qcom: add sa8775p-ride Rev 3 Bartosz Golaszewski
2024-06-26  8:59   ` Krzysztof Kozlowski
2024-06-26 11:02     ` Bartosz Golaszewski
2024-06-26 11:03       ` Krzysztof Kozlowski
2024-06-25 15:14 ` [PATCH v2 2/3] arm64: dts: qcom: move common parts for sa8775p-ride variants into a .dtsi Bartosz Golaszewski
2024-06-25 15:14 ` [PATCH v2 3/3] arm64: dts: qcom: sa8775p-ride-r3: add new board file Bartosz Golaszewski
2024-06-26 15:08   ` Konrad Dybcio [this message]
2024-06-25 15:18 ` [PATCH v2 0/3] arm64: dts: qcom: sa8775p-ride: support both board variants Bartosz Golaszewski
2024-06-26 13:31 ` Rob Herring (Arm)

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=5d0489e4-d04e-4ade-8fb4-b70ed5099d92@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=netdev@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).