From: Jakub Kicinski <kuba@kernel.org>
To: tsbogend@alpha.franken.de
Cc: Aleksander Jan Bajkowski <olek2@wp.pl>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
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: Tue, 19 Aug 2025 18:26:41 -0700 [thread overview]
Message-ID: <20250819182641.1b7ff210@kernel.org> (raw)
In-Reply-To: <20250817131022.3796476-1-olek2@wp.pl>
On Sun, 17 Aug 2025 14:49:05 +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.
Hi Thomas, Aleksander tagged these for net, are you okay with us taking
them via the networking tree? Looks like these are half DTS changes.
next prev parent reply other threads:[~2025-08-20 1:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 12:49 [PATCH net v2 0/2] mips: lantiq: fix ethernet support 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 ` Jakub Kicinski [this message]
2025-08-20 10:24 ` [PATCH net v2 0/2] mips: lantiq: fix ethernet support Thomas Bogendoerfer
2025-08-20 15:18 ` Jakub Kicinski
2025-08-22 20:05 ` Thomas Bogendoerfer
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=20250819182641.1b7ff210@kernel.org \
--to=kuba@kernel.org \
--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=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 \
--cc=tsbogend@alpha.franken.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.