From: Vladimir Oltean <olteanv@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: kuba@kernel.org, f.fainelli@gmail.com, vivien.didelot@gmail.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: dsa: don't print non-fatal MTU error if not supported
Date: Tue, 8 Sep 2020 04:08:06 +0300 [thread overview]
Message-ID: <20200908010806.innpkij2q7uf6s2p@skbuf> (raw)
In-Reply-To: <20200908005709.GB3267902@lunn.ch>
On Tue, Sep 08, 2020 at 02:57:09AM +0200, Andrew Lunn wrote:
> Hi Vladimir
>
> In some ways, this has been good. A lot more DSA drivers now have MTU
> support and jumbo packet support.
Yes, I suspect this is because many people wanted to experiment with
jumbo frames anyway, and the warning in dmesg acted as a sort of
reminder that the infrastructure is there. If it weren't for this
pre-existing interest, I would have expected a patch that silenced this
warning sooner, and not from me (the switches that I have don't print
this message).
Thanks,
-Vladimir
next prev parent reply other threads:[~2020-09-08 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 23:25 [PATCH net-next] net: dsa: don't print non-fatal MTU error if not supported Vladimir Oltean
2020-09-08 0:57 ` Andrew Lunn
2020-09-08 1:08 ` Vladimir Oltean [this message]
2020-09-08 3:06 ` Florian Fainelli
2020-09-08 4:01 ` Jakub Kicinski
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=20200908010806.innpkij2q7uf6s2p@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@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