From: patchwork-bot+netdevbpf@kernel.org
To: Junxiao Chang <junxiao.chang@intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
Joao.Pinto@synopsys.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, veekhee@gmail.com
Subject: Re: [PATCH net-next,v2] net: stmmac: remove duplicate dma queue channel macros
Date: Thu, 27 Oct 2022 10:20:15 +0000 [thread overview]
Message-ID: <166686601585.8143.16275733107810431975.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221025081747.1884926-1-junxiao.chang@intel.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 25 Oct 2022 16:17:47 +0800 you wrote:
> It doesn't need extra macros for queue 0 & 4. Same macro could
> be used for all 8 queues. Related queue/channel functions could
> be combined together.
>
> Original macro which has two same parameters is unsafe macro and
> might have potential side effects. Each MTL RxQ DMA channel mask
> is 4 bits, so using (0xf << chan) instead of GENMASK(x + 3, x) to
> avoid unsafe macro.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: stmmac: remove duplicate dma queue channel macros
https://git.kernel.org/netdev/net-next/c/330543d04f2c
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:[~2022-10-27 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 8:17 Junxiao Chang
2022-10-27 10:20 ` 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=166686601585.8143.16275733107810431975.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Joao.Pinto@synopsys.com \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=junxiao.chang@intel.com \
--cc=kuba@kernel.org \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=veekhee@gmail.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
all inboxes | Powered by JetHome®