From: patchwork-bot+netdevbpf@kernel.org
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, yangyingliang@huawei.com,
rmk+kernel@armlinux.org.uk, hi@atinb.me, michal.kubiak@intel.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
simon.horman@corigine.com, florian.fainelli@broadcom.com
Subject: Re: [net-next PATCH v3 1/5] net: dsa: tag_qca: return early if dev is not found
Date: Tue, 01 Aug 2023 11:10:22 +0000 [thread overview]
Message-ID: <169088822271.3908.11780275328908049417.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230730074113.21889-1-ansuelsmth@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 30 Jul 2023 09:41:09 +0200 you wrote:
> Currently checksum is recalculated and dsa tag stripped even if we later
> don't find the dev.
>
> To improve code, exit early if we don't find the dev and skip additional
> operation on the skb since it will be freed anyway.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> Reviewed-by: Simon Horman <simon.horman@corigine.com>
> Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
> Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
>
> [...]
Here is the summary with links:
- [net-next,v3,1/5] net: dsa: tag_qca: return early if dev is not found
https://git.kernel.org/netdev/net-next/c/de9db136dcc3
- [net-next,v3,2/5] net: dsa: qca8k: make learning configurable and keep off if standalone
https://git.kernel.org/netdev/net-next/c/23cfc7172e52
- [net-next,v3,3/5] net: dsa: qca8k: limit user ports access to the first CPU port on setup
https://git.kernel.org/netdev/net-next/c/18e8feae4a80
- [net-next,v3,4/5] net: dsa: qca8k: move qca8xxx hol fixup to separate function
https://git.kernel.org/netdev/net-next/c/a9108b0712bf
- [net-next,v3,5/5] net: dsa: qca8k: use dsa_for_each macro instead of for loop
https://git.kernel.org/netdev/net-next/c/01e6f8ad8d26
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-01 11:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 7:41 [net-next PATCH v3 1/5] net: dsa: tag_qca: return early if dev is not found Christian Marangi
2023-07-30 7:41 ` [net-next PATCH v3 2/5] net: dsa: qca8k: make learning configurable and keep off if standalone Christian Marangi
2023-07-30 7:41 ` [net-next PATCH v3 3/5] net: dsa: qca8k: limit user ports access to the first CPU port on setup Christian Marangi
2023-07-30 7:41 ` [net-next PATCH v3 4/5] net: dsa: qca8k: move qca8xxx hol fixup to separate function Christian Marangi
2023-07-31 23:09 ` Florian Fainelli
2023-07-30 7:41 ` [net-next PATCH v3 5/5] net: dsa: qca8k: use dsa_for_each macro instead of for loop Christian Marangi
2023-07-31 23:11 ` Florian Fainelli
2023-08-01 11:10 ` patchwork-bot+netdevbpf [this message]
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=169088822271.3908.11780275328908049417.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=hi@atinb.me \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=simon.horman@corigine.com \
--cc=yangyingliang@huawei.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).