From: patchwork-bot+netdevbpf@kernel.org
To: Xiaolei Wang <xiaolei.wang@windriver.com>
Cc: alexandre.torgue@foss.st.com, joabreu@synopsys.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com,
richardcochran@gmail.com, bartosz.golaszewski@linaro.org,
horms@kernel.org, rohan.g.thomas@intel.com,
rmk+kernel@armlinux.org.uk, fancer.lancer@gmail.com,
ahalaney@redhat.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [net/net-next PATCH v6 0/2] Move EST lock and EST structure to struct stmmac_priv
Date: Tue, 14 May 2024 01:40:30 +0000 [thread overview]
Message-ID: <171565083065.25298.6578381671622937855.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240513014346.1718740-1-xiaolei.wang@windriver.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 13 May 2024 09:43:44 +0800 you wrote:
> 1. Pulling the mutex protecting the EST structure out to avoid
> clearing it during reinit/memset of the EST structure,and
> reacquire the mutex lock when doing this initialization.
>
> 2. Moving the EST structure to a more logical location
>
> v1 -> v2:
> - move the lock to struct plat_stmmacenet_data
> v2 -> v3:
> - Add require the mutex lock for reinitialization
> v3 -> v4
> - Move est and est lock to stmmac_priv as suggested by Serge
> v4 -> v5
> - Submit it into two patches and add the Fixes tag
> v5 -> v6
> - move the stmmac_est structure declaration from
> include/linux/stmmac.h to
> drivers/net/ethernet/stmicro/stmmac/stmmac.h
>
> [...]
Here is the summary with links:
- [net,v6,1/2] net: stmmac: move the EST lock to struct stmmac_priv
https://git.kernel.org/netdev/net-next/c/36ac9e7f2e57
- [net-next,v6,2/2] net: stmmac: move the EST structure to struct stmmac_priv
https://git.kernel.org/netdev/net-next/c/bd17382ac36e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-05-14 1:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 1:43 [net/net-next PATCH v6 0/2] Move EST lock and EST structure to struct stmmac_priv Xiaolei Wang
2024-05-13 1:43 ` [net PATCH v6 1/2] net: stmmac: move the EST lock " Xiaolei Wang
2024-05-13 15:04 ` Andrew Halaney
2024-05-13 1:43 ` [net-next PATCH v6 2/2] net: stmmac: move the EST structure " Xiaolei Wang
2024-05-13 15:06 ` Andrew Halaney
2024-05-14 1: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=171565083065.25298.6578381671622937855.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ahalaney@redhat.com \
--cc=alexandre.torgue@foss.st.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fancer.lancer@gmail.com \
--cc=horms@kernel.org \
--cc=joabreu@synopsys.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=richardcochran@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rohan.g.thomas@intel.com \
--cc=xiaolei.wang@windriver.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 read-only IMAP folder(s) and NNTP newsgroup(s).