From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Petar Penkov <ppenkov.kernel@gmail.com>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH bpf-next 0/3] add gso_size to __sk_buff
Date: Tue, 3 Mar 2020 16:31:39 -0800 [thread overview]
Message-ID: <CAADnVQ+zbBuM1TYQ93CaGA3nKqVCS0ESKuo8M5NrXEQPPOEWvg@mail.gmail.com> (raw)
In-Reply-To: <CAGdtWsSd8sDoxTfW_Jcwc9u4sfHECKMzxt_GNjMTkWCbvKBr0A@mail.gmail.com>
On Tue, Mar 3, 2020 at 2:56 PM Petar Penkov <ppenkov.kernel@gmail.com> wrote:
>
> For the series: Acked-by: Petar Penkov <ppenkov@google.com>
please don't top post.
> On Tue, Mar 3, 2020 at 1:46 PM Willem de Bruijn
> <willemdebruijn.kernel@gmail.com> wrote:
> >
> > From: Willem de Bruijn <willemb@google.com>
> >
> > See first patch for details.
> >
> > Patch split across three parts { kernel feature, uapi header, tools }
> > following the custom for such __sk_buff changes.
Applied. Thanks
prev parent reply other threads:[~2020-03-04 0:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 20:05 [PATCH bpf-next 0/3] add gso_size to __sk_buff Willem de Bruijn
2020-03-03 20:05 ` [PATCH bpf-next 1/3] bpf: " Willem de Bruijn
2020-03-03 20:05 ` [PATCH bpf-next 2/3] bpf: Sync uapi bpf.h to tools/ Willem de Bruijn
2020-03-03 20:05 ` [PATCH bpf-next 3/3] selftests/bpf: test new __sk_buff field gso_size Willem de Bruijn
2020-03-03 22:56 ` [PATCH bpf-next 0/3] add gso_size to __sk_buff Petar Penkov
2020-03-04 0:31 ` 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+zbBuM1TYQ93CaGA3nKqVCS0ESKuo8M5NrXEQPPOEWvg@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=ppenkov.kernel@gmail.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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).