From: patchwork-bot+netdevbpf@kernel.org
To: Kevin Hao <haokexin@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, sgoutham@marvell.com,
gakula@marvell.com, sbhatta@marvell.com, hkelam@marvell.com,
netdev@vger.kernel.org, pavel@ucw.cz
Subject: Re: [PATCH net-next v2] net: octeontx2: Fix the confusion in buffer alloc failure path
Date: Wed, 10 Feb 2021 23:20:07 +0000 [thread overview]
Message-ID: <161299920743.13771.4953397169592654903.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210209101516.7536-1-haokexin@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Tue, 9 Feb 2021 18:15:16 +0800 you wrote:
> Pavel pointed that the return of dma_addr_t in
> otx2_alloc_rbuf/__otx2_alloc_rbuf() seem suspicious because a negative
> error code may be returned in some cases. For a dma_addr_t, the error
> code such as -ENOMEM does seem a valid value, so we can't judge if the
> buffer allocation fail or not based on that value. Add a parameter for
> otx2_alloc_rbuf/__otx2_alloc_rbuf() to store the dma address and make
> the return value to indicate if the buffer allocation really fail or
> not.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: octeontx2: Fix the confusion in buffer alloc failure path
https://git.kernel.org/netdev/net-next/c/1fb3ca767529
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-02-10 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 10:15 [PATCH net-next v2] net: octeontx2: Fix the confusion in buffer alloc failure path Kevin Hao
2021-02-10 19:29 ` Alexander Duyck
2021-02-10 23: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=161299920743.13771.4953397169592654903.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=haokexin@gmail.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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).