linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Song Liu <liu.song.a23@gmail.com>
To: Valdis Kletnieks <valdis.kletnieks@vt.edu>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Networking <netdev@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel/bpf/core.c - fix bitrotted kerneldoc.
Date: Tue, 29 Jan 2019 14:12:41 -0800	[thread overview]
Message-ID: <CAPhsuW6Jf3hThg5+BVFQC_iTS1m2psZS8pzmii+vzanfEcP_dA@mail.gmail.com> (raw)
In-Reply-To: <30924.1548734686@turing-police.cc.vt.edu>

On Mon, Jan 28, 2019 at 8:06 PM <valdis.kletnieks@vt.edu> wrote:
>
> Over the years, the function signature has changed, the kerneldoc block hasn't.
>
> Signed-off-by: Valdis Kletnieks <valdis.kletnieks@vt.edu>
Acked-by: Song Liu <songliubraving@fb.com>

>
> diff --git a/kernel/bpf/core.c b/kernel/bpf/core.c
> index 2a81b8af3748..2728b6247091 100644
> --- a/kernel/bpf/core.c
> +++ b/kernel/bpf/core.c
> @@ -1216,8 +1216,9 @@ bool bpf_opcode_in_insntable(u8 code)
>  #ifndef CONFIG_BPF_JIT_ALWAYS_ON
>  /**
>   *     __bpf_prog_run - run eBPF program on a given context
> - *     @ctx: is the data we are operating on
> + *     @regs: is the array of MAX_BPF_EXT_REG eBPF pseudo-registers
>   *     @insn: is the array of eBPF instructions
> + *     @stack: is the eBPF storage stack
>   *
>   * Decode and execute eBPF instructions.
>   */
>

      reply	other threads:[~2019-01-29 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29  4:04 [PATCH] kernel/bpf/core.c - fix bitrotted kerneldoc valdis.kletnieks
2019-01-29 22:12 ` Song Liu [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=CAPhsuW6Jf3hThg5+BVFQC_iTS1m2psZS8pzmii+vzanfEcP_dA@mail.gmail.com \
    --to=liu.song.a23@gmail.com \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=valdis.kletnieks@vt.edu \
    /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;
as well as URLs for NNTP newsgroup(s).