From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2VuIDx0b2tlQHJlZGhhdC5jb20+?=@ci.codeaurora.org
Cc: andrii@kernel.org, bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf] libbpf: restore errno return for functions that were already returning it
Date: Wed, 07 Jul 2021 04:30:03 +0000 [thread overview]
Message-ID: <162563220302.16281.6970918426494037005.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210706122355.236082-1-toke@redhat.com>
Hello:
This patch was applied to bpf/bpf.git (refs/heads/master):
On Tue, 6 Jul 2021 14:23:55 +0200 you wrote:
> The update to streamline libbpf error reporting intended to change all
> functions to return the errno as a negative return value if
> LIBBPF_STRICT_DIRECT_ERRS is set. However, if the flag is *not* set, the
> return value changes for the two functions that were already returning a
> negative errno unconditionally: bpf_link__unpin() and perf_buffer__poll().
>
> This is a user-visible API change that breaks applications; so let's revert
> these two functions back to unconditionally returning a negative errno
> value.
>
> [...]
Here is the summary with links:
- [bpf] libbpf: restore errno return for functions that were already returning it
https://git.kernel.org/bpf/bpf/c/af0efa050caa
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-07-07 4:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 12:23 [PATCH bpf] libbpf: restore errno return for functions that were already returning it Toke Høiland-Jørgensen
2021-07-07 4:30 ` 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=162563220302.16281.6970918426494037005.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2VuIDx0b2tlQHJlZGhhdC5jb20+?=@ci.codeaurora.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--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).