From: patchwork-bot+netdevbpf@kernel.org
To: EnDe Tan <ende.tan@starfivetech.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch,
alexandre.torgue@foss.st.com, joabreu@synopsys.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
leyfoon.tan@starfivetech.com, minda.chen@starfivetech.com,
endeneer@gmail.com, f.fainelli@gmail.com
Subject: Re: [net-next,v4,1/1] net: stmmac: Batch set RX OWN flag and other flags
Date: Thu, 05 Sep 2024 09:30:28 +0000 [thread overview]
Message-ID: <172552862851.1327461.7737934782782986812.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240831011114.2065912-1-ende.tan@starfivetech.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 31 Aug 2024 09:11:14 +0800 you wrote:
> From: Tan En De <ende.tan@starfivetech.com>
>
> Minimize access to the RX descriptor by collecting all the flags in a
> local variable and then updating the descriptor at once.
>
> Signed-off-by: Tan En De <ende.tan@starfivetech.com>
>
> [...]
Here is the summary with links:
- [net-next,v4,1/1] net: stmmac: Batch set RX OWN flag and other flags
https://git.kernel.org/netdev/net-next/c/d2095989943b
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:[~2024-09-05 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 1:11 [net-next,v4,1/1] net: stmmac: Batch set RX OWN flag and other flags ende.tan
2024-09-05 9:30 ` 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=172552862851.1327461.7737934782782986812.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ende.tan@starfivetech.com \
--cc=endeneer@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=minda.chen@starfivetech.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;
as well as URLs for NNTP newsgroup(s).