From: patchwork-bot+netdevbpf@kernel.org
To: Cai Huoqing <caihuoqing@baidu.com>
Cc: chris.snook@gmail.com, davem@davemloft.net, kuba@kernel.org,
michael.chan@broadcom.com, romieu@fr.zoreil.com,
steve.glendinning@shawell.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] net: atl1c: Fix a function name in print messages
Date: Mon, 27 Sep 2021 11:50:08 +0000 [thread overview]
Message-ID: <163274340813.15641.14226282330751565276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210925134014.251-1-caihuoqing@baidu.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Sat, 25 Sep 2021 21:40:10 +0800 you wrote:
> Use dma_map_single() instead of pci_map_single(),
> because the pci function wrappers are not called here.
>
> Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
> ---
> drivers/net/ethernet/atheros/atl1c/atl1c_main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- [v2,1/4] net: atl1c: Fix a function name in print messages
https://git.kernel.org/netdev/net-next/c/8d04c7b96424
- [v2,2/4] net: broadcom: Fix a function name in comments
https://git.kernel.org/netdev/net-next/c/8b58cba44e6b
- [v2,3/4] net: sis: Fix a function name in comments
https://git.kernel.org/netdev/net-next/c/e7e9d2088d9c
- [v2,4/4] net: smsc: Fix function names in print messages and comments
https://git.kernel.org/netdev/net-next/c/005552854fe6
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-09-27 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 13:40 [PATCH v2 1/4] net: atl1c: Fix a function name in print messages Cai Huoqing
2021-09-25 13:40 ` [PATCH v2 2/4] net: broadcom: Fix a function name in comments Cai Huoqing
2021-09-25 13:40 ` [PATCH v2 3/4] net: sis: " Cai Huoqing
2021-09-25 13:40 ` [PATCH v2 4/4] net: smsc: Fix function names in print messages and comments Cai Huoqing
2021-09-27 11: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=163274340813.15641.14226282330751565276.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=caihuoqing@baidu.com \
--cc=chris.snook@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=steve.glendinning@shawell.net \
/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).