From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
claudiu.manoil@nxp.com, yangbo.lu@nxp.com
Subject: Re: [PATCH net-next 0/2] enetc: trivial PTP one-step TX timestamping cleanups
Date: Thu, 21 Oct 2021 22:40:07 +0000 [thread overview]
Message-ID: <163485600735.31145.3968599007027017979.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211020174220.1093032-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 20 Oct 2021 20:42:18 +0300 you wrote:
> These are two cleanup patches for some inconsistencies I noticed in the
> driver's TX ring cleanup function.
>
> Vladimir Oltean (2):
> net: enetc: remove local "priv" variable in enetc_clean_tx_ring()
> net: enetc: use the skb variable directly in enetc_clean_tx_ring()
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: enetc: remove local "priv" variable in enetc_clean_tx_ring()
https://git.kernel.org/netdev/net-next/c/ae77bdbc2fc6
- [net-next,2/2] net: enetc: use the skb variable directly in enetc_clean_tx_ring()
https://git.kernel.org/netdev/net-next/c/520661495409
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:[~2021-10-21 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 17:42 [PATCH net-next 0/2] enetc: trivial PTP one-step TX timestamping cleanups Vladimir Oltean
2021-10-20 17:42 ` [PATCH net-next 1/2] net: enetc: remove local "priv" variable in enetc_clean_tx_ring() Vladimir Oltean
2021-10-20 17:42 ` [PATCH net-next 2/2] net: enetc: use the skb variable directly " Vladimir Oltean
2021-10-21 9:37 ` [PATCH net-next 0/2] enetc: trivial PTP one-step TX timestamping cleanups Claudiu Manoil
2021-10-21 22:40 ` 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=163485600735.31145.3968599007027017979.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vladimir.oltean@nxp.com \
--cc=yangbo.lu@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).