The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: John Keeping <john@metanate.com>,
	linux-perf-users@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	Nick Terrell <terrelln@fb.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] tools/build: drop slang include path in test-all
Date: Tue, 26 Oct 2021 11:25:18 -0300	[thread overview]
Message-ID: <YXgPzslee7oDIMPD@kernel.org> (raw)
In-Reply-To: <9acd33bf-a11b-2c2e-569f-0de4c971404f@gmail.com>

Em Mon, Oct 25, 2021 at 10:45:17AM -0700, Florian Fainelli escreveu:
> On 10/25/21 10:23 AM, John Keeping wrote:
> > Commit cbefd24f0aee3 ("tools build: Add test to check if slang.h is in
> > /usr/include/slang/") added a proper test to check whether slang.h is in
> > a subdirectory, and commit 1955c8cf5e26b ("perf tools: Don't hardcode
> > host include path for libslang") removed the include path for
> > test-libslang.bin but missed test-all.bin.  Apply the same change to
> > test-all.bin.
> > 
> > Fixes: 1955c8cf5e26 ("perf tools: Don't hardcode host include path for libslang")
> > Signed-off-by: John Keeping <john@metanate.com>
> 
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>

Thanks, applied.

- Arnaldo


      reply	other threads:[~2021-10-26 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 17:23 [PATCH RESEND] tools/build: drop slang include path in test-all John Keeping
2021-10-25 17:45 ` Florian Fainelli
2021-10-26 14:25   ` Arnaldo Carvalho de Melo [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=YXgPzslee7oDIMPD@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=f.fainelli@gmail.com \
    --cc=john@metanate.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=terrelln@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox