From: Jonathan Corbet <corbet@lwn.net>
To: Kees Cook <keescook@chromium.org>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Yang Shi <yang.shi@linaro.org>,
Dave Anderson <danderson@google.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] bpf: doc: "neg" opcode has no operands
Date: Thu, 31 Mar 2016 00:32:03 -0600 [thread overview]
Message-ID: <20160331003203.33f8b7bb@lwn.net> (raw)
In-Reply-To: <20160328215647.GA23746@www.outflux.net>
On Mon, 28 Mar 2016 14:56:47 -0700
Kees Cook <keescook@chromium.org> wrote:
> From: Dave Anderson <danderson@google.com>
>
> Fixes a copy-paste-o in the BPF opcode table: "neg" takes no arguments
> and thus has no addressing modes.
I've applied this to the docs tree, thanks.
jon
prev parent reply other threads:[~2016-03-31 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 21:56 [PATCH] bpf: doc: "neg" opcode has no operands Kees Cook
2016-03-29 0:32 ` Alexei Starovoitov
2016-03-29 7:57 ` Daniel Borkmann
2016-03-31 6:32 ` Jonathan Corbet [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=20160331003203.33f8b7bb@lwn.net \
--to=corbet@lwn.net \
--cc=ast@kernel.org \
--cc=danderson@google.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yang.shi@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.