From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: pull-request: bpf 2018-11-27
Date: Tue, 27 Nov 2018 09:52:29 -0800 (PST) [thread overview]
Message-ID: <20181127.095229.1162940838625218449.davem@davemloft.net> (raw)
In-Reply-To: <20181127091617.10125-1-daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Tue, 27 Nov 2018 10:16:17 +0100
> The following pull-request contains BPF updates for your *net* tree.
>
> The main changes are:
>
> 1) Fix several bugs in BPF sparc JIT, that is, convergence for fused
> branches, initialization of frame pointer register, and moving all
> arguments into output registers from input registers in prologue
> to fix BPF to BPF calls, from David.
>
> 2) Fix a bug in arm64 JIT for fetching BPF to BPF call addresses where
> they are not guaranteed to fit into imm field and therefore must be
> retrieved through prog aux data, from Daniel.
>
> 3) Explicitly add all JITs to MAINTAINERS file with developers able to
> help out in feature development, fixes, review, etc.
Pulled, thanks Daniel.
prev parent reply other threads:[~2018-11-28 4:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 9:16 pull-request: bpf 2018-11-27 Daniel Borkmann
2018-11-27 17:52 ` David Miller [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=20181127.095229.1162940838625218449.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--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).