From: patchwork-bot+netdevbpf@kernel.org
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: davem@davemloft.net, kuba@kernel.org, kaixuxia@tencent.com,
mhabets@solarflare.com, mst@redhat.com,
luc.vanoostenryck@gmail.com, jesse.brandeburg@intel.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/2] net: pch_gbe: Use dma_set_mask_and_coherent to simplify code
Date: Tue, 24 Nov 2020 01:10:05 +0000 [thread overview]
Message-ID: <160618020532.30283.4433703176583925818.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201121090302.1332491-1-christophe.jaillet@wanadoo.fr>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Sat, 21 Nov 2020 10:03:02 +0100 you wrote:
> 'pci_set_dma_mask()' + 'pci_set_consistent_dma_mask()' can be replaced by
> an equivalent 'dma_set_mask_and_coherent()' which is much less verbose.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> .../net/ethernet/oki-semi/pch_gbe/pch_gbe_main.c | 14 ++++----------
> 1 file changed, 4 insertions(+), 10 deletions(-)
Here is the summary with links:
- [1/2] net: pch_gbe: Use dma_set_mask_and_coherent to simplify code
https://git.kernel.org/netdev/net-next/c/8ff39301efd9
- [2/2] net: pch_gbe: Use 'dma_free_coherent()' to undo 'dma_alloc_coherent()'
https://git.kernel.org/netdev/net-next/c/7fd6372e273e
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:[~2020-11-24 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 9:03 [PATCH 1/2] net: pch_gbe: Use dma_set_mask_and_coherent to simplify code Christophe JAILLET
2020-11-24 1:10 ` 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=160618020532.30283.4433703176583925818.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=jesse.brandeburg@intel.com \
--cc=kaixuxia@tencent.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=mhabets@solarflare.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
/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).