From: patchwork-bot+netdevbpf@kernel.org
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
yatsenko@meta.com
Subject: Re: [PATCH bpf-next v3 0/4] libbpf: stringify error codes in log messages
Date: Tue, 12 Nov 2024 04:40:29 +0000 [thread overview]
Message-ID: <173138642925.82002.2282388771258860402.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241111212919.368971-1-mykyta.yatsenko5@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 11 Nov 2024 21:29:15 +0000 you wrote:
> From: Mykyta Yatsenko <yatsenko@meta.com>
>
> Libbpf may report error in 2 ways:
> 1. Numeric errno
> 2. Errno's text representation, returned by strerror
> Both ways may be confusing for users: numeric code requires people to
> know how to find its meaning and strerror may be too generic and
> unclear.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/4] libbpf: introduce errstr() for stringifying errno
https://git.kernel.org/bpf/bpf-next/c/1633a83bf993
- [bpf-next,v3,2/4] libbpf: stringify errno in log messages in libbpf.c
https://git.kernel.org/bpf/bpf-next/c/271abf041cb3
- [bpf-next,v3,3/4] libbpf: stringify errno in log messages in btf*.c
https://git.kernel.org/bpf/bpf-next/c/af8380d51948
- [bpf-next,v3,4/4] libbpf: stringify errno in log messages in the remaining code
https://git.kernel.org/bpf/bpf-next/c/4ce16ddd7105
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:[~2024-11-12 4:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 21:29 [PATCH bpf-next v3 0/4] libbpf: stringify error codes in log messages Mykyta Yatsenko
2024-11-11 21:29 ` [PATCH bpf-next v3 1/4] libbpf: introduce errstr() for stringifying errno Mykyta Yatsenko
2024-11-12 4:35 ` Andrii Nakryiko
2024-11-11 21:29 ` [PATCH bpf-next v3 2/4] libbpf: stringify errno in log messages in libbpf.c Mykyta Yatsenko
2024-11-11 21:29 ` [PATCH bpf-next v3 3/4] libbpf: stringify errno in log messages in btf*.c Mykyta Yatsenko
2024-11-11 21:29 ` [PATCH bpf-next v3 4/4] libbpf: stringify errno in log messages in the remaining code Mykyta Yatsenko
2024-11-12 4:40 ` 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=173138642925.82002.2282388771258860402.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=yatsenko@meta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.