From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: netdev@vger.kernel.org, linux-kbuild@vger.kernel.org,
bblanco@plumgrid.com, naveen.n.rao@linux.vnet.ibm.com,
borkmann@iogearbox.net
Subject: Re: [net-next PATCH V2 2/5] samples/bpf: Makefile verify LLVM compiler avail and bpf target is supported
Date: Tue, 26 Apr 2016 10:28:39 -0700 [thread overview]
Message-ID: <20160426172837.GC42777@ast-mbp.thefacebook.com> (raw)
In-Reply-To: <20160426162716.22962.36473.stgit@firesoul>
On Tue, Apr 26, 2016 at 06:27:16PM +0200, Jesper Dangaard Brouer wrote:
> Make compiling samples/bpf more user friendly, by detecting if LLVM
> compiler tool 'llc' is available, and also detect if the 'bpf' target
> is available in this version of LLVM.
>
> Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
Acked-by: Alexei Starovoitov <ast@kernel.org>
next prev parent reply other threads:[~2016-04-26 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 16:27 [net-next PATCH V2 0/5] samples/bpf: Improve user experience Jesper Dangaard Brouer
2016-04-26 16:27 ` [net-next PATCH V2 1/5] samples/bpf: add back functionality to redefine LLC command Jesper Dangaard Brouer
2016-04-26 17:28 ` Alexei Starovoitov
2016-04-26 16:27 ` [net-next PATCH V2 2/5] samples/bpf: Makefile verify LLVM compiler avail and bpf target is supported Jesper Dangaard Brouer
2016-04-26 17:28 ` Alexei Starovoitov [this message]
2016-04-27 13:52 ` David Laight
2016-04-26 16:27 ` [net-next PATCH V2 3/5] samples/bpf: add a README file to get users started Jesper Dangaard Brouer
2016-04-26 17:31 ` Alexei Starovoitov
2016-04-27 6:30 ` Jesper Dangaard Brouer
2016-04-26 16:27 ` [net-next PATCH V2 4/5] samples/bpf: allow make to be run from samples/bpf/ directory Jesper Dangaard Brouer
2016-04-26 17:31 ` Alexei Starovoitov
2016-04-26 16:27 ` [net-next PATCH V2 5/5] samples/bpf: like LLC also verify and allow redefining CLANG command Jesper Dangaard Brouer
2016-04-26 17:36 ` Alexei Starovoitov
2016-04-27 6:45 ` Jesper Dangaard Brouer
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=20160426172837.GC42777@ast-mbp.thefacebook.com \
--to=alexei.starovoitov@gmail.com \
--cc=bblanco@plumgrid.com \
--cc=borkmann@iogearbox.net \
--cc=brouer@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--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