From: Vladimir Oltean <olteanv@gmail.com>
To: Pawel Dembicki <paweldembicki@gmail.com>
Cc: netdev@vger.kernel.org, Linus Walleij <linus.walleij@linaro.org>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: dsa: vsc73xx: fix MTU configuration
Date: Thu, 29 Jun 2023 00:44:42 +0300 [thread overview]
Message-ID: <20230628214442.5wucuusl6pqudllk@skbuf> (raw)
In-Reply-To: <20230628194327.1765644-1-paweldembicki@gmail.com>
On Wed, Jun 28, 2023 at 09:43:27PM +0200, Pawel Dembicki wrote:
> Switch in MAXLEN register stores the maximum size of a data frame.
> The MTU size is 18 bytes smaller than the frame size.
>
> The current settings are causing problems with packet forwarding.
> This patch fixes the MTU settings to proper values.
>
> Fixes: fb77ffc6ec86 ("net: dsa: vsc73xx: make the MTU configurable")
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
>
> ---
> In my first attempt, I sent it to net-next [0], but I was asked to resend
> it to net.
>
> [0]https://lore.kernel.org/netdev/20230625115343.1603330-7-paweldembicki@gmail.com/
Just like you had marked those earlier patches as "[PATCH net-next]",
this should have also been marked as "[PATCH v2 net]". Patchwork does
complain about that and deduced the wrong tree, but accepted it anyway
and otherwise ran its tests.
https://patchwork.kernel.org/project/netdevbpf/patch/20230628194327.1765644-1-paweldembicki@gmail.com/
I don't believe there is any reason to resend this patch.
Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
next prev parent reply other threads:[~2023-06-28 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 19:43 [PATCH] net: dsa: vsc73xx: fix MTU configuration Pawel Dembicki
2023-06-28 21:44 ` Vladimir Oltean [this message]
2023-06-30 0:40 ` patchwork-bot+netdevbpf
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=20230628214442.5wucuusl6pqudllk@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paweldembicki@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