From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: pull-request: bpf-next 2017-12-28
Date: Wed, 27 Dec 2017 20:41:08 -0500 (EST) [thread overview]
Message-ID: <20171227.204108.334274235776263929.davem@davemloft.net> (raw)
In-Reply-To: <20171228001821.5305-1-daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Thu, 28 Dec 2017 01:18:21 +0100
> The following pull-request contains BPF updates for your *net-next*
> tree.
Pulled.
Any progress on those tests failing on strict alignment architectures?
next prev parent reply other threads:[~2017-12-28 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 0:18 pull-request: bpf-next 2017-12-28 Daniel Borkmann
2017-12-28 1:41 ` David Miller [this message]
2017-12-28 20:19 ` Daniel Borkmann
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=20171227.204108.334274235776263929.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox