From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Daniel Borkmann <daniel@iogearbox.net>, davem@davemloft.net
Cc: kuba@kernel.org, ast@kernel.org, andrii.nakryiko@gmail.com,
netdev@vger.kernel.org, bpf@vger.kernel.org,
Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Subject: Re: pull-request: bpf 2021-10-26
Date: Thu, 28 Oct 2021 11:17:38 +0200 [thread overview]
Message-ID: <878ryda4p9.fsf@toke.dk> (raw)
In-Reply-To: <07334aca-9b58-fdae-0de9-43d44e087d76@iogearbox.net>
Daniel Borkmann <daniel@iogearbox.net> writes:
> On 10/28/21 12:03 AM, Toke Høiland-Jørgensen wrote:
>> Daniel Borkmann <daniel@iogearbox.net> writes:
>>
>>> The following pull-request contains BPF updates for your *net* tree.
>>>
>>> We've added 12 non-merge commits during the last 7 day(s) which contain
>>> a total of 23 files changed, 118 insertions(+), 98 deletions(-).
>>
>> Hi Daniel
>>
>> Any chance we could also get bpf merged into bpf-next? We'd like to use
>> this fix:
>>
>>> 1) Fix potential race window in BPF tail call compatibility check,
>>> from Toke Høiland-Jørgensen.
>
> Makes sense! I presume final net tree PR before merge win might go out today
> or tomorrow (Jakub/David?) and would get fast-fwd'ed into net-next after that
> as well, which means we get the current batch for bpf-next out by then. By
> that we'd have mentioned commit in bpf-next after re-sync.
Alright, sounds good - thanks! :)
-Toke
prev parent reply other threads:[~2021-10-28 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 20:19 pull-request: bpf 2021-10-26 Daniel Borkmann
2021-10-26 23:40 ` patchwork-bot+netdevbpf
2021-10-27 22:03 ` Toke Høiland-Jørgensen
2021-10-27 22:13 ` Daniel Borkmann
2021-10-28 9:17 ` Toke Høiland-Jørgensen [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=878ryda4p9.fsf@toke.dk \
--to=toke@redhat.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--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).