From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Luiz Angelo Daros de Luca <luizluca@gmail.com>,
Kurt Kanzenbach <kurt@linutronix.de>,
George McCollister <george.mccollister@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH net-next v2] docs: net: dsa: describe issues with checksum offload
Date: Wed, 13 Apr 2022 21:00:26 +0000 [thread overview]
Message-ID: <20220413210026.pe4jpq7jjefcuypo@skbuf> (raw)
In-Reply-To: <Ylc5RhzehbIuLswA@lunn.ch>
On Wed, Apr 13, 2022 at 10:57:42PM +0200, Andrew Lunn wrote:
> > I meant to ask about the actual mv88e6060 driver, the one that uses
> > tag_trailer.c, not mv88e6xxx.
>
> Ah, sorry, i don't have one of those. And i've no idea of anybody who
> does. It is a long long time since i heard of anybody with one.
>
> Andrew
Ok, I'll go with "no checksum offload for its trailer tag, and bugs
never fixed because no one uses it", in any case no Sasquatch. Thanks.
next prev parent reply other threads:[~2022-04-13 21:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 23:03 [PATCH net-next v2] docs: net: dsa: describe issues with checksum offload Luiz Angelo Daros de Luca
2022-04-13 20:08 ` Vladimir Oltean
2022-04-13 20:49 ` Andrew Lunn
2022-04-13 20:53 ` Vladimir Oltean
2022-04-13 20:57 ` Andrew Lunn
2022-04-13 21:00 ` Vladimir Oltean [this message]
2022-04-14 2:48 ` Luiz Angelo Daros de Luca
2022-04-14 12:58 ` Vladimir Oltean
2022-04-15 8:01 ` Luiz Angelo Daros de Luca
2022-04-15 10:22 ` Vladimir Oltean
2022-04-16 5:30 ` Luiz Angelo Daros de Luca
2022-04-13 20:56 ` Andrew Lunn
2022-04-14 6:29 ` Kurt Kanzenbach
2022-04-14 15:22 ` Vladimir Oltean
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=20220413210026.pe4jpq7jjefcuypo@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox