BPF List
 help / color / mirror / Atom feed
From: Peter Wu <peter@lekensteyn.nl>
To: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: [PATCH v2 0/4] BPF-related documentation fixes
Date: Wed, 21 Aug 2019 00:08:56 +0100	[thread overview]
Message-ID: <20190820230900.23445-1-peter@lekensteyn.nl> (raw)

Hi,

Here are some small doc updates that should hopefully save the next
eBPF/uprobe user some time. Based on v5.3-rc2, but net-next appears to
have no conflicts.

Changes since the v1[1]:
- Split bpf.h patch for kernel and userspace tools (requested by Alexei)
- Add new 'bpf: clarify when bpf_trace_printk discards lines' patch.

Kind regards,
Peter

 [1]: https://lkml.kernel.org/r/20190819212122.10286-1-peter@lekensteyn.nl

Peter Wu (4):
  bpf: clarify description for CONFIG_BPF_EVENTS
  bpf: fix 'struct pt_reg' typo in documentation
  bpf: clarify when bpf_trace_printk discards lines
  bpf: sync bpf.h to tools/

 include/uapi/linux/bpf.h       | 8 +++++---
 kernel/trace/Kconfig           | 3 ++-
 tools/include/uapi/linux/bpf.h | 8 +++++---
 3 files changed, 12 insertions(+), 7 deletions(-)

-- 
2.22.0


             reply	other threads:[~2019-08-20 23:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 23:08 Peter Wu [this message]
2019-08-20 23:08 ` [PATCH v2 1/4] bpf: clarify description for CONFIG_BPF_EVENTS Peter Wu
2019-08-20 23:08 ` [PATCH v2 2/4] bpf: fix 'struct pt_reg' typo in documentation Peter Wu
2019-08-21 10:28   ` Quentin Monnet
2019-08-20 23:08 ` [PATCH v2 3/4] bpf: clarify when bpf_trace_printk discards lines Peter Wu
2019-08-20 23:22   ` Alexei Starovoitov
2019-08-21  0:04     ` Peter Wu
2019-08-21 17:23       ` Alexei Starovoitov
2019-08-20 23:09 ` [PATCH v2 4/4] bpf: sync bpf.h to tools/ Peter Wu

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=20190820230900.23445-1-peter@lekensteyn.nl \
    --to=peter@lekensteyn.nl \
    --cc=ast@kernel.org \
    --cc=bpf@vger.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