From: patchwork-bot+netdevbpf@kernel.org
To: Florent Revest <revest@chromium.org>
Cc: bpf@vger.kernel.org, viro@zeniv.linux.org.uk,
davem@davemloft.net, kuba@kernel.org, ast@kernel.org,
daniel@iogearbox.net, kafai@fb.com, yhs@fb.com,
andrii@kernel.org, kpsingh@chromium.org, revest@google.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
kpsingh@google.com
Subject: Re: [PATCH bpf-next v5 1/6] net: Remove the err argument from sock_from_file
Date: Fri, 04 Dec 2020 22:00:07 +0000 [thread overview]
Message-ID: <160711920795.26112.15547923878362487061.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201204113609.1850150-1-revest@google.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 4 Dec 2020 12:36:04 +0100 you wrote:
> Currently, the sock_from_file prototype takes an "err" pointer that is
> either not set or set to -ENOTSOCK IFF the returned socket is NULL. This
> makes the error redundant and it is ignored by a few callers.
>
> This patch simplifies the API by letting callers deduce the error based
> on whether the returned socket is NULL or not.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/6] net: Remove the err argument from sock_from_file
https://git.kernel.org/bpf/bpf-next/c/dba4a9256bb4
- [bpf-next,v5,2/6] bpf: Add a bpf_sock_from_file helper
https://git.kernel.org/bpf/bpf-next/c/4f19cab76136
- [bpf-next,v5,3/6] bpf: Expose bpf_sk_storage_* to iterator programs
https://git.kernel.org/bpf/bpf-next/c/a50a85e40c59
- [bpf-next,v5,4/6] selftests/bpf: Add an iterator selftest for bpf_sk_storage_delete
https://git.kernel.org/bpf/bpf-next/c/593f6d41abbb
- [bpf-next,v5,5/6] selftests/bpf: Add an iterator selftest for bpf_sk_storage_get
https://git.kernel.org/bpf/bpf-next/c/bd9b327e58f9
- [bpf-next,v5,6/6] selftests/bpf: Test bpf_sk_storage_get in tcp iterators
https://git.kernel.org/bpf/bpf-next/c/34da87213d3d
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:[~2020-12-04 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 11:36 [PATCH bpf-next v5 1/6] net: Remove the err argument from sock_from_file Florent Revest
2020-12-04 11:36 ` [PATCH bpf-next v5 2/6] bpf: Add a bpf_sock_from_file helper Florent Revest
2020-12-04 11:36 ` [PATCH bpf-next v5 3/6] bpf: Expose bpf_sk_storage_* to iterator programs Florent Revest
2020-12-04 11:36 ` [PATCH bpf-next v5 4/6] selftests/bpf: Add an iterator selftest for bpf_sk_storage_delete Florent Revest
2020-12-04 11:36 ` [PATCH bpf-next v5 5/6] selftests/bpf: Add an iterator selftest for bpf_sk_storage_get Florent Revest
2020-12-04 11:36 ` [PATCH bpf-next v5 6/6] selftests/bpf: Test bpf_sk_storage_get in tcp iterators Florent Revest
2020-12-04 22:00 ` 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=160711920795.26112.15547923878362487061.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=davem@davemloft.net \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=kpsingh@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=revest@chromium.org \
--cc=revest@google.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yhs@fb.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).