From: Florian Fainelli <f.fainelli@gmail.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>, netdev@vger.kernel.org
Cc: andrew@lunn.ch, vivien.didelot@gmail.com, kuba@kernel.org,
Christian Eggers <ceggers@arri.de>,
Kurt Kanzenbach <kurt@linutronix.de>,
Per Forlin <per.forlin@axis.com>,
Oleksij Rempel <linux@rempel-privat.de>
Subject: Re: [PATCH v3 net-next 12/12] net: dsa: tag_ar9331: let DSA core deal with TX reallocation
Date: Mon, 2 Nov 2020 12:52:41 -0800 [thread overview]
Message-ID: <21df9110-3989-41be-7397-4ea5a775619e@gmail.com> (raw)
In-Reply-To: <20201101191620.589272-13-vladimir.oltean@nxp.com>
On 11/1/2020 11:16 AM, Vladimir Oltean wrote:
> Now that we have a central TX reallocation procedure that accounts for
> the tagger's needed headroom in a generic way, we can remove the
> skb_cow_head call.
>
> Cc: Per Forlin <per.forlin@axis.com>
> Cc: Oleksij Rempel <linux@rempel-privat.de>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
> Tested-by: Oleksij Rempel <linux@rempel-privat.de>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2020-11-02 20:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 19:16 [PATCH v3 net-next 00/12] Generic TX reallocation for DSA Vladimir Oltean
2020-11-01 19:16 ` [PATCH v3 net-next 01/12] net: dsa: implement a central TX reallocation procedure Vladimir Oltean
2020-11-02 20:43 ` Florian Fainelli
2020-11-01 19:16 ` [PATCH v3 net-next 02/12] net: dsa: tag_ksz: don't allocate additional memory for padding/tagging Vladimir Oltean
2020-11-02 20:44 ` Florian Fainelli
2020-11-01 19:16 ` [PATCH v3 net-next 03/12] net: dsa: trailer: " Vladimir Oltean
2020-11-02 20:44 ` Florian Fainelli
2020-11-01 19:16 ` [PATCH v3 net-next 04/12] net: dsa: tag_qca: let DSA core deal with TX reallocation Vladimir Oltean
2020-11-02 20:45 ` Florian Fainelli
2020-11-01 19:16 ` [PATCH v3 net-next 05/12] net: dsa: tag_ocelot: " Vladimir Oltean
2020-11-02 20:45 ` Florian Fainelli
2020-11-01 19:16 ` [PATCH v3 net-next 06/12] net: dsa: tag_mtk: " Vladimir Oltean
2020-11-02 20:45 ` Florian Fainelli
2020-11-01 19:16 ` [PATCH v3 net-next 07/12] net: dsa: tag_lan9303: " Vladimir Oltean
2020-11-02 20:51 ` Florian Fainelli
2020-11-01 19:16 ` [PATCH v3 net-next 08/12] net: dsa: tag_edsa: " Vladimir Oltean
2020-11-02 20:51 ` Florian Fainelli
2020-11-01 19:16 ` [PATCH v3 net-next 09/12] net: dsa: tag_brcm: " Vladimir Oltean
2020-11-02 20:34 ` Florian Fainelli
2020-11-03 10:51 ` Vladimir Oltean
2020-11-03 17:04 ` Jakub Kicinski
2020-11-03 18:15 ` Vladimir Oltean
2020-11-03 18:34 ` Jakub Kicinski
2020-11-03 17:32 ` Florian Fainelli
2020-11-03 18:00 ` Vladimir Oltean
2020-11-01 19:16 ` [PATCH v3 net-next 10/12] net: dsa: tag_dsa: " Vladimir Oltean
2020-11-02 20:52 ` Florian Fainelli
2020-11-01 19:16 ` [PATCH v3 net-next 11/12] net: dsa: tag_gswip: " Vladimir Oltean
2020-11-02 20:52 ` Florian Fainelli
2020-11-01 19:16 ` [PATCH v3 net-next 12/12] net: dsa: tag_ar9331: " Vladimir Oltean
2020-11-02 20:52 ` Florian Fainelli [this message]
2020-11-03 1:43 ` [PATCH v3 net-next 00/12] Generic TX reallocation for DSA 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=21df9110-3989-41be-7397-4ea5a775619e@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=ceggers@arri.de \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux@rempel-privat.de \
--cc=netdev@vger.kernel.org \
--cc=per.forlin@axis.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).