netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Andrey Ignatov <rdna@fb.com>
Cc: Network Development <netdev@vger.kernel.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Yonghong Song <yhs@fb.com>, Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH bpf-next 0/3] bpf: Allow narrow loads with offset > 0
Date: Sat, 10 Nov 2018 15:38:08 -0800	[thread overview]
Message-ID: <CAADnVQ+x5Cc-D+QydqF6CXv0-VvfML_h-b58hinWOksDLy9=3A@mail.gmail.com> (raw)
In-Reply-To: <20181110191345.vbqst4ephtfxk2jx@ast-mbp.dhcp.thefacebook.com>

On Sat, Nov 10, 2018 at 11:13 AM Alexei Starovoitov
<alexei.starovoitov@gmail.com> wrote:
>
> On Tue, Nov 06, 2018 at 05:23:25PM -0800, Andrey Ignatov wrote:
> > This patch set adds support for narrow loads with offset > 0 to BPF
> > verifier.
> >
> > Patch 1 provides more details and is the main patch in the set.
> > Patches 2 and 3 add new test cases to test_verifier and test_sock_addr
> > selftests.
>
> Applied, Thanks

reverted.
please fix compiler warning and respin.

      reply	other threads:[~2018-11-11  9:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07  1:23 [PATCH bpf-next 0/3] bpf: Allow narrow loads with offset > 0 Andrey Ignatov
2018-11-07  1:23 ` [PATCH bpf-next 1/3] " Andrey Ignatov
2018-11-07  1:23 ` [PATCH bpf-next 2/3] selftests/bpf: Test narrow loads with off > 0 in test_verifier Andrey Ignatov
2018-11-07  1:23 ` [PATCH bpf-next 3/3] selftests/bpf: Test narrow loads with off > 0 for bpf_sock_addr Andrey Ignatov
2018-11-10 19:13 ` [PATCH bpf-next 0/3] bpf: Allow narrow loads with offset > 0 Alexei Starovoitov
2018-11-10 23:38   ` Alexei Starovoitov [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='CAADnVQ+x5Cc-D+QydqF6CXv0-VvfML_h-b58hinWOksDLy9=3A@mail.gmail.com' \
    --to=alexei.starovoitov@gmail.com \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=rdna@fb.com \
    --cc=yhs@fb.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 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).