All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Usama Arif <usama.arif@bytedance.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	fam.zheng@bytedance.com, cong.wang@bytedance.com,
	song@kernel.org, quentin@isovalent.com,
	andrii.nakryiko@gmail.com
Subject: Re: [PATCH bpf-next v3 1/3] uapi/bpf: Add missing description and returns for helper documentation
Date: Wed, 19 Jan 2022 18:40:09 +0000	[thread overview]
Message-ID: <164261760975.14405.8285375089710473745.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220119114442.1452088-1-usama.arif@bytedance.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Wed, 19 Jan 2022 11:44:40 +0000 you wrote:
> Both description and returns section will become mandatory
> for helpers and syscalls in a later commit to generate man pages.
> 
> This commit also adds in the documentation that BPF_PROG_RUN is
> an alias for BPF_PROG_TEST_RUN for anyone searching for the
> syscall in the generated man pages.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/3] uapi/bpf: Add missing description and returns for helper documentation
    https://git.kernel.org/bpf/bpf-next/c/e40fbbf0572c
  - [bpf-next,v3,2/3] bpf/scripts: Make description and returns section for helpers/syscalls mandatory
    https://git.kernel.org/bpf/bpf-next/c/f1f3f67fd8ed
  - [bpf-next,v3,3/3] bpf/scripts: Raise an exception if the correct number of sycalls are not generated
    https://git.kernel.org/bpf/bpf-next/c/0ba3929e5b3d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-01-19 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 11:44 [PATCH bpf-next v3 1/3] uapi/bpf: Add missing description and returns for helper documentation Usama Arif
2022-01-19 11:44 ` [PATCH bpf-next v3 2/3] bpf/scripts: Make description and returns section for helpers/syscalls mandatory Usama Arif
2022-01-19 11:44 ` [PATCH bpf-next v3 3/3] bpf/scripts: Raise an exception if the correct number of sycalls are not generated Usama Arif
2022-01-19 18:40 ` patchwork-bot+netdevbpf [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=164261760975.14405.8285375089710473745.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=cong.wang@bytedance.com \
    --cc=daniel@iogearbox.net \
    --cc=fam.zheng@bytedance.com \
    --cc=quentin@isovalent.com \
    --cc=song@kernel.org \
    --cc=usama.arif@bytedance.com \
    /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.