From: patchwork-bot+netdevbpf@kernel.org
To: Wong Vee Khee <vee.khee.wong@linux.intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
mcoquelin.stm32@gmail.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: [PATCH net-next 0/2] stmmac: intel: minor clean-up
Date: Sat, 12 Jun 2021 20:20:04 +0000 [thread overview]
Message-ID: <162352920446.6609.10045548501109238922.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210611131609.1685105-1-vee.khee.wong@linux.intel.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 11 Jun 2021 21:16:07 +0800 you wrote:
> This patch series include two minor-cleanup patches:
>
> 1. Move all the hardcoded DEFINEs to dwmac-intel header file.
> 2. Fix the wrong kernel-doc on the intel_eth_pci_remove() function.
>
> Since the changes are minor, only basic sanity tests are done on a
> Intel TigerLake with Marvell88E2110 PHY:-
>
> [...]
Here is the summary with links:
- [net-next,1/2] stmmac: intel: move definitions to dwmac-intel header file
https://git.kernel.org/netdev/net-next/c/fb9349c4163e
- [net-next,2/2] stmmac: intel: fix wrong kernel-doc
https://git.kernel.org/netdev/net-next/c/3c3ea630e87c
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-06-12 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 13:16 [PATCH net-next 0/2] stmmac: intel: minor clean-up Wong Vee Khee
2021-06-11 13:16 ` [PATCH net-next 1/2] stmmac: intel: move definitions to dwmac-intel header file Wong Vee Khee
2021-06-11 13:16 ` [PATCH net-next 2/2] stmmac: intel: fix wrong kernel-doc Wong Vee Khee
2021-06-12 20: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=162352920446.6609.10045548501109238922.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--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=peppe.cavallaro@st.com \
--cc=vee.khee.wong@linux.intel.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).