From: Daniel Borkmann <daniel@iogearbox.net>
To: Jakub Kicinski <jakub.kicinski@netronome.com>, netdev@vger.kernel.org
Cc: oss-drivers@netronome.com, alexei.starovoitov@gmail.com
Subject: Re: [PATCH net-next 0/2] tools: bpftool: clean up and extend Makefiles
Date: Fri, 8 Dec 2017 20:46:05 +0100 [thread overview]
Message-ID: <8f48b422-8f89-bd1d-5830-295319ab1142@iogearbox.net> (raw)
In-Reply-To: <20171207230018.7510-1-jakub.kicinski@netronome.com>
On 12/08/2017 12:00 AM, Jakub Kicinski wrote:
> Hi!
>
> This is a follow up to a series of Makefile fixes for bpftool from
> two weeks ago. I think there will have to be a merge back of net-next
> into bpf-next (or rebase), AFAICT the previous series arrived in
> net-next already, but not in bpf-next. I hope that makes sense.
> FWIW this should not conflict with Roman's cgroup work.
>
> Quentin says:
>
> First patch of this series cleans up the two Makefiles (Makefile and
> Documentation/Makefile) and make their contents more consistent.
>
> The second one add "uninstall" and "doc-uninstall" targets, to remove files
> previously installed on the system with "install" and "doc-install"
> targets.
Series applied to bpf-next, thanks guys!
prev parent reply other threads:[~2017-12-08 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 23:00 [PATCH net-next 0/2] tools: bpftool: clean up and extend Makefiles Jakub Kicinski
2017-12-07 23:00 ` [PATCH net-next 1/2] tools: bpftool: harmonise Makefile and Documentation/Makefile Jakub Kicinski
2017-12-07 23:00 ` [PATCH net-next 2/2] tools: bpftool: create "uninstall", "doc-uninstall" make targets Jakub Kicinski
2017-12-13 11:16 ` Arnaldo Carvalho de Melo
2017-12-08 19:46 ` Daniel Borkmann [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=8f48b422-8f89-bd1d-5830-295319ab1142@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.