All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Chenbo Feng <chenbofeng.kernel@gmail.com>
Cc: netdev@vger.kernel.org, mic@digikod.net, Chenbo Feng <fengc@google.com>
Subject: Re: [PATCH net-next] Fix inaccurate helper function description
Date: Thu, 27 Apr 2017 13:10:27 +0200	[thread overview]
Message-ID: <5901D1A3.9090207@iogearbox.net> (raw)
In-Reply-To: <1493250083-1954-1-git-send-email-chenbofeng.kernel@gmail.com>

On 04/27/2017 01:41 AM, Chenbo Feng wrote:
> From: Chenbo Feng <fengc@google.com>
>
> The description inside uapi/linux/bpf.h about bpf_get_socket_uid
> helper function is no longer valid. It returns overflowuid rather
> than 0 when failed.
>
> Signed-off-by: Chenbo Feng <fengc@google.com>

"bpf: " prefix in patch subject line would have been good.

Acked-by: Daniel Borkmann <daniel@iogearbox.net>

  reply	other threads:[~2017-04-27 11:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 23:41 [PATCH net-next] Fix inaccurate helper function description Chenbo Feng
2017-04-27 11:10 ` Daniel Borkmann [this message]
2017-04-28  3:55   ` Alexei Starovoitov
2017-05-01  2:25 ` David Miller

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=5901D1A3.9090207@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=chenbofeng.kernel@gmail.com \
    --cc=fengc@google.com \
    --cc=mic@digikod.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 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.