From: Nick Bowler <nbowler@draconx.ca>
To: Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: PROBLEM: Broken or delayed ethernet on Xilinx ZCU104 since 5.18 (regression)
Date: Fri, 4 Aug 2023 12:28:37 -0400 [thread overview]
Message-ID: <CADyTPEwvxrEUnHtMq==nUC7ai8AR-N_1CHXErkQo4Pbfcx0OKQ@mail.gmail.com> (raw)
In-Reply-To: <CADyTPEwgG0=R_b5DNBP0J0auDXu2BNTOwkSUFg-s7pLJUPC+Tg@mail.gmail.com>
On 2023-08-04, Nick Bowler <nbowler@draconx.ca> wrote:
> As far as I can see, this is supposed to be handled by the code in
> drivers/reset/zynqmp-reset.c driver, it is enabled by CONFIG_ARCH_ZYNQMP,
> and I have that set to "y", and it appears to be getting compiled in (that
> is, there is a drivers/reset/zynqmp-reset.o file in the build directory).
Correction: I typed zynqmp-reset.c but file is actually reset-zynqmp.c.
Cheers,
Nick
next prev parent reply other threads:[~2023-08-04 16:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 15:26 PROBLEM: Broken or delayed ethernet on Xilinx ZCU104 since 5.18 (regression) Nick Bowler
2023-08-04 15:45 ` Linux regression tracking (Thorsten Leemhuis)
2023-08-08 16:00 ` Robert Hancock
2023-08-04 15:52 ` Rob Herring
2023-08-04 16:24 ` Nick Bowler
2023-08-04 16:28 ` Nick Bowler [this message]
2023-08-04 16:47 ` Russell King (Oracle)
2023-08-04 16:54 ` Nick Bowler
2023-08-04 17:02 ` Rob Herring
2023-08-04 17:52 ` Nick Bowler
2023-08-04 20:22 ` Rob Herring
2023-08-04 21:31 ` Nick Bowler
2023-08-04 22:27 ` Russell King (Oracle)
2023-08-05 6:57 ` Nick Bowler
2023-08-05 7:03 ` Andrew Lunn
2023-08-05 6:58 ` Andrew Lunn
2023-08-05 7:10 ` Nick Bowler
2023-08-05 7:25 ` Andrew Lunn
2023-08-05 7:34 ` Nick Bowler
2023-08-29 13:30 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-08-05 1:03 ` Saravana Kannan
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='CADyTPEwvxrEUnHtMq==nUC7ai8AR-N_1CHXErkQo4Pbfcx0OKQ@mail.gmail.com' \
--to=nbowler@draconx.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--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).