From: patchwork-bot+netdevbpf@kernel.org
To: Daire McNamara <daire.mcnamara@microchip.com>
Cc: nicolas.ferre@microchip.com, claudiu.beznea@microchip.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
conor.dooley@microchip.com
Subject: Re: [PATCH v4 0/1] Adjust macb max_tx_len for mpfs
Date: Sat, 13 May 2023 19:50:18 +0000 [thread overview]
Message-ID: <168400741837.29282.2422245224869605594.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230512122032.2902335-1-daire.mcnamara@microchip.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 12 May 2023 13:20:31 +0100 you wrote:
> From: Daire McNamara <daire.mcnamara@microchip.com>
>
> Several customers have reported unexpected ethernet issues whereby
> the GEM stops transmitting and receiving. Performing an action such
> as ifconfig <ethX> down; ifconfig <ethX> up clears this particular
> condition.
>
> [...]
Here is the summary with links:
- [v4,1/1] net: macb: Shorten max_tx_len to 4KiB - 56 on mpfs
https://git.kernel.org/netdev/net-next/c/314cf958de2a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-05-13 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 12:20 [PATCH v4 0/1] Adjust macb max_tx_len for mpfs daire.mcnamara
2023-05-12 12:20 ` [PATCH v4 1/1] net: macb: Shorten max_tx_len to 4KiB - 56 on mpfs daire.mcnamara
2023-05-12 12:23 ` Conor Dooley
2023-05-12 15:11 ` Simon Horman
2023-05-13 8:51 ` Claudiu.Beznea
2023-05-13 19:50 ` patchwork-bot+netdevbpf [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=168400741837.29282.2422245224869605594.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.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 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.