From: YueHaibing <yuehaibing@huawei.com>
To: <patchwork-bot+netdevbpf@kernel.org>,
zhengyongjun <zhengyongjun3@huawei.com>
Cc: <jmaloy@redhat.com>, <ying.xue@windriver.com>,
<davem@davemloft.net>, <kuba@kernel.org>,
<netdev@vger.kernel.org>, <tipc-discussion@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] tipc: Return the correct errno code
Date: Tue, 8 Jun 2021 10:15:58 +0800 [thread overview]
Message-ID: <410bbe52-5ead-4719-d711-8dc355a9a5f4@huawei.com> (raw)
In-Reply-To: <162284160438.23356.17911968954229324185.git-patchwork-notify@kernel.org>
On 2021/6/5 5:20, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
>
> This patch was applied to netdev/net-next.git (refs/heads/master):
This should not be applied.
tipc_node_xmit() now check -ENOBUFS rather than -ENOMEM.
Yongjun, maybe you fix this now?
>
> On Fri, 4 Jun 2021 09:47:02 +0800 you wrote:
>> When kalloc or kmemdup failed, should return ENOMEM rather than ENOBUF.
>>
>> Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>
>> ---
>> net/tipc/link.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> Here is the summary with links:
> - [net-next] tipc: Return the correct errno code
> https://git.kernel.org/netdev/net-next/c/0efea3c649f0
>
> You are awesome, thank you!
> --
> Deet-doot-dot, I am a bot.
> https://korg.docs.kernel.org/patchwork/pwbot.html
>
>
> .
>
next prev parent reply other threads:[~2021-06-08 2:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 1:47 [PATCH net-next] tipc: Return the correct errno code Zheng Yongjun
2021-06-04 1:34 ` 答复: " zhengyongjun
2021-08-02 8:02 ` Hoang Huu Le
2021-08-02 8:52 ` 答复: " zhengyongjun
2021-06-04 21:20 ` patchwork-bot+netdevbpf
2021-06-08 2:15 ` YueHaibing [this message]
2021-06-08 2:35 ` 答复: " zhengyongjun
2021-06-08 2:39 ` zhengyongjun
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=410bbe52-5ead-4719-d711-8dc355a9a5f4@huawei.com \
--to=yuehaibing@huawei.com \
--cc=davem@davemloft.net \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.com \
--cc=zhengyongjun3@huawei.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).