From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Network Development <netdev@vger.kernel.org>,
Stanislav Fomichev <sdf@google.com>
Cc: Soheil Hassas Yeganeh <soheil@google.com>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH internal pre-review] bpf: add missing entries to bpf_helpers.h
Date: Tue, 26 Feb 2019 18:00:44 -0500 [thread overview]
Message-ID: <CAF=yD-KUTTPEmvG5k6qQ9uoguM5s6wGZ1yLovnMO6jbdRo8MRw@mail.gmail.com> (raw)
In-Reply-To: <20190226225553.214360-1-willemdebruijn.kernel@gmail.com>
On Tue, Feb 26, 2019 at 5:55 PM Willem de Bruijn
<willemdebruijn.kernel@gmail.com> wrote:
>
> From: Willem de Bruijn <willemb@google.com>
>
> Signed-off-by: Willem de Bruijn <willemb@google.com>
As the topic indicated I did not intend to send for review to netdev@
just yet. Apologies for the spam.
For one, this commit lacks a commit message.
That said. It is out there, so any comments welcome, thanks.
next prev parent reply other threads:[~2019-02-26 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 22:55 [PATCH internal pre-review] bpf: add missing entries to bpf_helpers.h Willem de Bruijn
2019-02-26 22:59 ` Soheil Hassas Yeganeh
2019-02-26 23:00 ` Willem de Bruijn [this message]
2019-02-27 6:52 ` Martin Lau
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='CAF=yD-KUTTPEmvG5k6qQ9uoguM5s6wGZ1yLovnMO6jbdRo8MRw@mail.gmail.com' \
--to=willemdebruijn.kernel@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=soheil@google.com \
--cc=willemb@google.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).