netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Björn Töpel" <bjorn.topel@gmail.com>
To: linux-kernel@vger.kernel.org, acme@kernel.org
Cc: "Björn Töpel" <bjorn.topel@gmail.com>,
	netdev@vger.kernel.org, bpf@vger.kernel.org, ast@kernel.org,
	daniel@iogearbox.net, adrian.hunter@intel.com, jolsa@kernel.org,
	namhyung@kernel.org
Subject: [PATCH 0/2] perf tools: optional compile time test_attr__* depenency for perf-sys.h
Date: Tue,  1 Oct 2019 13:33:05 +0200	[thread overview]
Message-ID: <20191001113307.27796-1-bjorn.topel@gmail.com> (raw)

This mini series makes it possible to disable the use of test_attr__*
for perf-sys.h users outside perf. E.g., samples/bpf/ uses perf-sys.h
as a syscall wrapper.

Now a user can define HAVE_ATTR_TEST to zero to avoid this, and as a
nice side-effect it also fixes the samples/bpf/ build. ;-)

Björn Töpel (2):
  perf tools: Make usage of test_attr__* optional for perf-sys.h
  samples/bpf: fix build by setting HAVE_ATTR_TEST to zero

 samples/bpf/Makefile  | 1 +
 tools/perf/perf-sys.h | 6 ++++--
 2 files changed, 5 insertions(+), 2 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-10-01 11:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 11:33 Björn Töpel [this message]
2019-10-01 11:33 ` [PATCH 1/2] perf tools: Make usage of test_attr__* optional for perf-sys.h Björn Töpel
2019-10-02 21:00   ` Song Liu
2019-10-03 13:50   ` Arnaldo Carvalho de Melo
2019-10-15  5:31   ` [tip: perf/core] " tip-bot2 for Björn Töpel
2019-10-01 11:33 ` [PATCH 2/2] samples/bpf: fix build by setting HAVE_ATTR_TEST to zero Björn Töpel
2019-10-02 21:00   ` Song Liu
2019-10-03  0:19     ` KP Singh
2019-10-03 13:53       ` Arnaldo Carvalho de Melo
2019-10-15  5:31   ` [tip: perf/core] " tip-bot2 for Björn Töpel

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=20191001113307.27796-1-bjorn.topel@gmail.com \
    --to=bjorn.topel@gmail.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@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;
as well as URLs for NNTP newsgroup(s).