U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@kernel.org>
To: Tom Rini <trini@konsulko.com>
Cc: Joe Hershberger <joe.hershberger@ni.com>,
	Ramon Fried <rfried.dev@gmail.com>, Nishanth Menon <nm@ti.com>,
	Robert Nelson <robertcnelson@gmail.com>,
	Wadim Egorov <w.egorov@phytec.de>,
	Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	Simon Glass <sjg@chromium.org>,
	srk@ti.com, s-vadapalli@ti.com, vigneshr@ti.com,
	r-gunasekaran@ti.com, danishanwar@ti.com, u-boot@lists.denx.de
Subject: Re: [PATCH 0/3] arm: dts: am62-beagleplay: Fix Beagleplay Ethernet
Date: Fri, 10 May 2024 22:24:41 +0300	[thread overview]
Message-ID: <08b22e06-f316-4ef6-bd42-a4600f1f8035@kernel.org> (raw)
In-Reply-To: <20240510130830.GT2568172@bill-the-cat>



On 10/05/2024 16:08, Tom Rini wrote:
> On Fri, May 10, 2024 at 12:55:15PM +0300, Roger Quadros wrote:
>> Tom,
>>
>> On 25/04/2024 15:20, Roger Quadros wrote:
>>> Sync AM62 device tree files with Linux v6.9-rc5 and
>>> add in the missing bits in -u-boot.dtsi to get CPSW
>>> Ethernet working.
>>>
>>> The last patch is marked [not-for-merge] as it is not yet
>>> applied to Linux device tree.
>>>
>>> CI testing
>>> https://github.com/u-boot/u-boot/pull/527
>>
>> While the checks have passed, there are some recent conflicts introduced
>>
>> Conflicting files
>> arch/arm/dts/k3-am62-phycore-som.dtsi
>> arch/arm/dts/k3-am625-phyboard-lyra-rdk.dts 
>>
>> Those files have been removed.
>>
>> Do you want me to rebase and resend this series?
> 
> Since part 3 was a do not merge I wasn't sure what the end goal of this
> series was.
> 

Goal was to show what is required to get Ethernet working and DT synced with kernel.org.
part 3 can now be merged as the commit is now in linux-next. [1]

Maybe it is best if I rebase and send this as v2 and drop the do-not-merge for patch 3?

[1] arm64: dts: ti: beagleplay: Fix Ethernet PHY RESET GPIOs
      commit: 0b1133ee36ecbf3b02f69cc4e8a169f1b6019e40
-- 
cheers,
-roger

  reply	other threads:[~2024-05-10 19:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 12:20 [PATCH 0/3] arm: dts: am62-beagleplay: Fix Beagleplay Ethernet Roger Quadros
2024-04-25 12:20 ` [PATCH 1/3] arm: dts: k3-am62*: sync with Linux v6.9-rc5 Roger Quadros
2024-04-25 12:20 ` [PATCH 2/3] arm: dts: k3-am625-beagleplay: get CPSW Ethernet to work Roger Quadros
2024-04-25 12:20 ` [PATCH not-for-merge 3/3] arm: dts: k3-am625-beagleplay: Fix Ethernet PHY reset GPIO Roger Quadros
2024-05-10  9:55 ` [PATCH 0/3] arm: dts: am62-beagleplay: Fix Beagleplay Ethernet Roger Quadros
2024-05-10 13:08   ` Tom Rini
2024-05-10 19:24     ` Roger Quadros [this message]
2024-05-10 19:33       ` Tom Rini
2024-05-10 19:58         ` Nishanth Menon
2024-05-10 20:00           ` Tom Rini
2024-05-10 20:01             ` Tom Rini

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=08b22e06-f316-4ef6-bd42-a4600f1f8035@kernel.org \
    --to=rogerq@kernel.org \
    --cc=danishanwar@ti.com \
    --cc=joe.hershberger@ni.com \
    --cc=marcel.ziswiler@toradex.com \
    --cc=nm@ti.com \
    --cc=r-gunasekaran@ti.com \
    --cc=rfried.dev@gmail.com \
    --cc=robertcnelson@gmail.com \
    --cc=s-vadapalli@ti.com \
    --cc=sjg@chromium.org \
    --cc=srk@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@ti.com \
    --cc=w.egorov@phytec.de \
    /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