From: Sirio Balmelli <sirio@b-ad.ch>
To: daniel@iogearbox.net
Cc: netdev@vger.kernel.org
Subject: [PATCH v2 0/2] selftests/bpf
Date: Mon, 30 Apr 2018 09:17:08 +0200 [thread overview]
Message-ID: <20180430071706.sn4vochr64mxkum4@vm4> (raw)
Thank you for reviewing earlier patch :)
Resubmitting with a saner include chain.
I was unsure whether to reply to your mail directly or submit an entirely new
set of patches marked 'v2'; apologies if this breaks the workflow.
Sirio Balmelli (2):
selftests/bpf: Makefile: add includes to fix broken test build
selftests/bpf: update .gitignore files
tools/bpf/bpftool/.gitignore | 12 ++++++++++++
tools/testing/selftests/bpf/.gitignore | 1 +
tools/testing/selftests/bpf/Makefile | 10 ++++++++--
3 files changed, 21 insertions(+), 2 deletions(-)
create mode 100644 tools/bpf/bpftool/.gitignore
--
2.7.4
reply other threads:[~2018-04-30 7:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180430071706.sn4vochr64mxkum4@vm4 \
--to=sirio@b-ad.ch \
--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