From: patchwork-bot+netdevbpf@kernel.org
To: Joakim Zhang <qiangqing.zhang@nxp.com>
Cc: davem@davemloft.net, kuba@kernel.org, peppe.cavallaro@st.com,
alexandre.torgue@foss.st.com, joabreu@synopsys.com,
mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com
Subject: Re: [PATCH net 0/2] net: fixes for fec ptp
Date: Wed, 16 Jun 2021 19:50:04 +0000 [thread overview]
Message-ID: <162387300499.13042.8545046199906380662.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210616091426.13694-1-qiangqing.zhang@nxp.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Wed, 16 Jun 2021 17:14:24 +0800 you wrote:
> Small fixes for fec ptp.
>
> Fugang Duan (1):
> net: fec_ptp: add clock rate zero check
>
> Joakim Zhang (1):
> net: fec_ptp: fix issue caused by refactor the fec_devtype
>
> [...]
Here is the summary with links:
- [net,1/2] net: fec_ptp: add clock rate zero check
https://git.kernel.org/netdev/net/c/cb3cefe3f3f8
- [net,2/2] net: fec_ptp: fix issue caused by refactor the fec_devtype
https://git.kernel.org/netdev/net/c/d23765646e71
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-16 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 9:14 [PATCH net 0/2] net: fixes for fec ptp Joakim Zhang
2021-06-16 9:14 ` [PATCH net 1/2] net: fec_ptp: add clock rate zero check Joakim Zhang
2021-06-16 10:20 ` Russell King (Oracle)
2021-06-16 11:40 ` Joakim Zhang
2021-06-16 13:28 ` Russell King (Oracle)
2021-06-16 9:14 ` [PATCH net 2/2] net: fec_ptp: fix issue caused by refactor the fec_devtype Joakim Zhang
2021-06-16 19:50 ` 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=162387300499.13042.8545046199906380662.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-imx@nxp.com \
--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=qiangqing.zhang@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).