bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: "Daniel T. Lee" <danieltimlee@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andriin@fb.com>,
	Networking <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH,bpf-next 1/2] samples: bpf: update outdated error message
Date: Tue, 5 Nov 2019 18:15:53 -0800	[thread overview]
Message-ID: <CAEf4BzYreS_bAOKZMsCpxh1sCbJbaVY3DmmmPUUwkYgNK4wjKQ@mail.gmail.com> (raw)
In-Reply-To: <20191105225111.4940-2-danieltimlee@gmail.com>

On Tue, Nov 5, 2019 at 2:51 PM Daniel T. Lee <danieltimlee@gmail.com> wrote:
>
> Currently, under samples, several methods are being used to load bpf
> program.
>
> Since using libbpf is preferred solution, lots of previously used
> 'load_bpf_file' from bpf_load are replaced with 'bpf_prog_load_xattr'
> from libbpf.
>
> But some of the error messages still show up as 'load_bpf_file' instead
> of 'bpf_prog_load_xattr'.
>
> This commit fixes outdated errror messages under samples and fixes some
> code style issues.
>
> Signed-off-by: Daniel T. Lee <danieltimlee@gmail.com>
> ---

Acked-by: Andrii Nakryiko <andriin@fb.com>

[...]

  reply	other threads:[~2019-11-06  2:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 22:51 [PATCH,bpf-next 0/2] samples: bpf: update map definition to new syntax BTF-defined map Daniel T. Lee
2019-11-05 22:51 ` [PATCH,bpf-next 1/2] samples: bpf: update outdated error message Daniel T. Lee
2019-11-06  2:15   ` Andrii Nakryiko [this message]
2019-11-05 22:51 ` [PATCH,bpf-next 2/2] samples: bpf: update map definition to new syntax BTF-defined map Daniel T. Lee
2019-11-06  2:14   ` Andrii Nakryiko
2019-11-07  0:44     ` Daniel T. Lee

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=CAEf4BzYreS_bAOKZMsCpxh1sCbJbaVY3DmmmPUUwkYgNK4wjKQ@mail.gmail.com \
    --to=andrii.nakryiko@gmail.com \
    --cc=andriin@fb.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=danieltimlee@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).