From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Luiz Angelo Daros de Luca <luizluca@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
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: Fri, 15 Apr 2022 10:22:29 +0000 [thread overview]
Message-ID: <20220415102229.zaoqqjxcs27ofdy3@skbuf> (raw)
In-Reply-To: <CAJq09z6XTz7Xb0VBFdFVELb26LztFng7hULe6tSDX7KCQjzUmg@mail.gmail.com>
On Fri, Apr 15, 2022 at 05:01:46AM -0300, Luiz Angelo Daros de Luca wrote:
> That looks like a larger change.
Well, you asked what are the options in the unlikely event that we'll
see offloading DSA masters for tail tags.
> Should we put this patch on hold waiting for the code refactor or we
> merge it as is (as it tells no lies about current code).
It looks like the patch was marked as "changes requested", my side
comments other than the Reviewed-by tag were probably misinterpreted:
https://patchwork.kernel.org/project/netdevbpf/patch/20220411230305.28951-1-luizluca@gmail.com/
So please repost.
next prev parent reply other threads:[~2022-04-15 10:22 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
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 [this message]
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=20220415102229.zaoqqjxcs27ofdy3@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