[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167096881701.16694.14250332414378810386.git-patchwork-notify@kernel.org>
Date: Tue, 13 Dec 2022 22:00:17 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Xin Liu <liuxin350@...wei.com>
Cc: andrii@...nel.org, ast@...nel.org, daniel@...earbox.net,
martin.lau@...ux.dev, song@...nel.org, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org, sdf@...gle.com,
haoluo@...gle.com, jolsa@...nel.org, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org, yanan@...wei.com,
wuchangye@...wei.com, xiesongyang@...wei.com,
kongweibin2@...wei.com, zhangmingyi5@...wei.com
Subject: Re: [PATCH bpf-next v3] libbpf: Optimized return value in libbpf_strerror
when errno is libbpf errno
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Sat, 10 Dec 2022 16:20:45 +0800 you wrote:
> This is a small improvement in libbpf_strerror. When libbpf_strerror
> is used to obtain the system error description, if the length of the
> buf is insufficient, libbpf_sterror returns ERANGE and sets errno to
> ERANGE.
>
> However, this processing is not performed when the error code
> customized by libbpf is obtained. Make some minor improvements here,
> return -ERANGE and set errno to ERANGE when buf is not enough for
> custom description.
>
> [...]
Here is the summary with links:
- [bpf-next,v3] libbpf: Optimized return value in libbpf_strerror when errno is libbpf errno
https://git.kernel.org/bpf/bpf-next/c/c2614f627941
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists