From: David Miller <davem@redhat.com>
To: brouer@redhat.com
Cc: linux-kbuild@vger.kernel.org, netdev@vger.kernel.org,
acme@kernel.org, borkmann@iogearbox.net,
alexei.starovoitov@gmail.com
Subject: Re: [net-next PATCH] samples/bpf: adjust Makefile and README.rst
Date: Mon, 11 Nov 2019 21:42:37 -0800 (PST) [thread overview]
Message-ID: <20191111.214237.704198386375428842.davem@redhat.com> (raw)
In-Reply-To: <157340347607.14617.683175264051058224.stgit@firesoul>
From: Jesper Dangaard Brouer <brouer@redhat.com>
Date: Sun, 10 Nov 2019 17:31:16 +0100
> Side effect of some kbuild changes resulted in breaking the
> documented way to build samples/bpf/.
>
> This patch change the samples/bpf/Makefile to work again, when
> invoking make from the subdir samples/bpf/. Also update the
> documentation in README.rst, to reflect the new way to build.
>
> Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
Applied.
prev parent reply other threads:[~2019-11-12 5:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 16:31 [net-next PATCH] samples/bpf: adjust Makefile and README.rst Jesper Dangaard Brouer
2019-11-11 13:49 ` Daniel Borkmann
2019-11-11 13:56 ` Jesper Dangaard Brouer
2019-11-11 14:30 ` Daniel Borkmann
2019-11-12 5:42 ` David Miller [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=20191111.214237.704198386375428842.davem@redhat.com \
--to=davem@redhat.com \
--cc=acme@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=borkmann@iogearbox.net \
--cc=brouer@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--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