From: Vineet Gupta <vineet.gupta@linux.dev>
To: bpf@vger.kernel.org
Cc: bpf@gcc.gnu.org, jose.marchesi@oracle.com, ast@kernel.org,
Eduard Zingerman <eddyz87@gmail.com>,
Yonghong Song <yonghong.song@linux.dev>,
Vineet Gupta <vineet.gupta@linux.dev>
Subject: [PATCH v2 0/2] BPF documentation improvements
Date: Thu, 2 Apr 2026 15:13:37 -0700 [thread overview]
Message-ID: <20260402221339.1614989-1-vineet.gupta@linux.dev> (raw)
Hi,
A couple of patches for documentation as I start to hack on gcc-bpf backend.
Changes since v1 captured in individual patches.
Thx,
-Vineet
Vineet Gupta (2):
bpf, doc: Clarify Pseudo-C notation and w vs r register usage
bpf, doc: Improve MOV/MOVSX documentation and add examples
.../bpf/standardization/instruction-set.rst | 61 +++++++++++++++----
1 file changed, 48 insertions(+), 13 deletions(-)
--
2.53.0
next reply other threads:[~2026-04-02 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 22:13 Vineet Gupta [this message]
2026-04-02 22:13 ` [PATCH v2 1/2] bpf, doc: Clarify Pseudo-C notation and w vs r register usage Vineet Gupta
2026-04-02 22:13 ` [PATCH v2 2/2] bpf, doc: Improve MOV/MOVSX documentation and add examples Vineet Gupta
2026-04-03 5:27 ` bot+bpf-ci
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=20260402221339.1614989-1-vineet.gupta@linux.dev \
--to=vineet.gupta@linux.dev \
--cc=ast@kernel.org \
--cc=bpf@gcc.gnu.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=jose.marchesi@oracle.com \
--cc=yonghong.song@linux.dev \
/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