From: Daniel Borkmann <daniel@iogearbox.net>
To: Arthur Fabre <arthur@arthurfabre.com>,
Alexei Starovoitov <ast@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jonathan Corbet <corbet@lwn.net>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] bpf, doc: Document Jump X addressing mode
Date: Mon, 8 Oct 2018 10:22:11 +0200 [thread overview]
Message-ID: <b4246d37-26c0-36c7-908d-e01b20c23028@iogearbox.net> (raw)
In-Reply-To: <20181007084519.27445-1-arthur@arthurfabre.com>
On 10/07/2018 10:45 AM, Arthur Fabre wrote:
> bpf_asm and the other classic BPF tools support jump conditions
> comparing register A to register X, in addition to comparing register A
> with constant K.
> Only the latter was documented in filter.txt, add two new addressing
> modes that describe the former.
>
> Signed-off-by: Arthur Fabre <arthur@arthurfabre.com>
Applied to bpf-next, thanks!
prev parent reply other threads:[~2018-10-08 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 8:45 [PATCH] bpf, doc: Document Jump X addressing mode Arthur Fabre
2018-10-08 8:22 ` Daniel Borkmann [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=b4246d37-26c0-36c7-908d-e01b20c23028@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=arthur@arthurfabre.com \
--cc=ast@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=linux-doc@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