From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, john@phrozen.org,
devicetree@vger.kernel.org, netdev@vger.kernel.org,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] mips: lantiq: fix ethernet support
Date: Fri, 22 Aug 2025 22:05:37 +0200 [thread overview]
Message-ID: <aKjNkagCFYlZTFXn@alpha.franken.de> (raw)
In-Reply-To: <20250817131022.3796476-1-olek2@wp.pl>
On Sun, Aug 17, 2025 at 02:49:05PM +0200, Aleksander Jan Bajkowski wrote:
> This series fixes broken Ethernet in the upstream danube dts. The
> driver doesn't attach due to missing burst length property. OpenWRT
> has its own dts, which is correct, so the problem has only been
> spotted now. Other dts inconsistencies with bindings have been
> fixed as well.
>
> ---
> Changes in v2:
> - renaming clocks in sysctrl
> ---
> Aleksander Jan Bajkowski (2):
> mips: dts: lantiq: danube: add missing burst length property
> mips: lantiq: xway: sysctrl: rename the etop node
>
> arch/mips/boot/dts/lantiq/danube_easy50712.dts | 5 ++++-
> arch/mips/lantiq/xway/sysctrl.c | 10 +++++-----
> 2 files changed, 9 insertions(+), 6 deletions(-)
series applied to mips-fixes.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2025-08-22 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 12:49 Aleksander Jan Bajkowski
2025-08-17 12:49 ` [PATCH net v2 1/2] mips: dts: lantiq: danube: add missing burst length property Aleksander Jan Bajkowski
2025-08-17 12:49 ` [PATCH net v2 2/2] mips: lantiq: xway: sysctrl: rename the etop node Aleksander Jan Bajkowski
2025-08-20 1:26 ` [PATCH net v2 0/2] mips: lantiq: fix ethernet support Jakub Kicinski
2025-08-20 10:24 ` Thomas Bogendoerfer
2025-08-20 15:18 ` Jakub Kicinski
2025-08-22 20:05 ` Thomas Bogendoerfer [this message]
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=aKjNkagCFYlZTFXn@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=john@phrozen.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=pabeni@redhat.com \
--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
all inboxes | Powered by JetHome®