From: Kurt Kanzenbach <kurt@linutronix.de>
To: Johannes Zink <j.zink@pengutronix.de>,
Richard Cochran <richardcochran@gmail.com>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Russell King <linux@armlinux.org.uk>,
kernel test robot <lkp@intel.com>,
Eric Dumazet <edumazet@google.com>,
Jose Abreu <joabreu@synopsys.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org,
patchwork-jzi@pengutronix.de
Subject: Re: [PATCH v2] net: stmmac: correct MAC propagation delay
Date: Thu, 27 Jul 2023 09:15:40 +0200 [thread overview]
Message-ID: <873519u8o3.fsf@kurt> (raw)
In-Reply-To: <8742d597-e8b1-705f-6616-dca4ead529f4@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
Hi Johannes, Richard,
On Thu Jul 27 2023, Johannes Zink wrote:
>> BTW this driver is actually for an IP core used in many, many SoCs.
>>
>> How many _other_ SoCs did you test your patch on?
>>
> I don't have many available, thus as stated in the description: on the i.MX8MP
> only. That's why I am implementing my stuff in the imx glue code, you're
> welcome to help testing on other hardware if you have any at hand.
I can assist with testing on Intel real time platforms, stm32mp1 and
Cyclone V (and imx8mp). Just Cc me on the next the version of this
patch.
Thanks,
Kurt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2023-07-27 7:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 10:01 [PATCH v2] net: stmmac: correct MAC propagation delay Johannes Zink
2023-07-26 3:06 ` Jakub Kicinski
2023-07-26 3:22 ` Richard Cochran
2023-07-26 3:39 ` Jakub Kicinski
2023-07-26 6:04 ` Marc Kleine-Budde
2023-07-26 15:34 ` Richard Cochran
2023-07-27 6:40 ` Johannes Zink
2023-07-27 13:30 ` Richard Cochran
2023-07-26 6:10 ` Johannes Zink
2023-07-26 15:43 ` Richard Cochran
2023-07-27 6:39 ` Johannes Zink
2023-07-27 6:55 ` Johannes Zink
2023-07-27 7:41 ` Johannes Zink
2023-07-27 7:15 ` Kurt Kanzenbach [this message]
2023-07-27 7:18 ` Johannes Zink
2023-07-26 5:50 ` Marc Kleine-Budde
2023-07-26 3:50 ` patchwork-bot+netdevbpf
2023-07-26 18:00 ` Richard Cochran
2023-07-27 6:42 ` Johannes Zink
2023-07-27 13:34 ` Richard Cochran
2023-07-26 20:57 ` Richard Cochran
2023-07-27 7:20 ` Johannes Zink
2023-07-27 13:36 ` Richard Cochran
2023-07-31 7:00 ` Johannes Zink
2023-07-31 13:44 ` Richard Cochran
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=873519u8o3.fsf@kurt \
--to=kurt@linutronix.de \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.zink@pengutronix.de \
--cc=joabreu@synopsys.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-jzi@pengutronix.de \
--cc=peppe.cavallaro@st.com \
--cc=richardcochran@gmail.com \
/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