From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: mhiramat@kernel.org, acme@redhat.com, akpm@linux-foundation.org,
bp@alien8.de, geert@linux-m68k.org, jolsa@redhat.com,
masahiroy@kernel.org, michal.lkml@markovi.net,
peterz@infradead.org, rdunlap@infradead.org, rostedt@goodmis.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] tools: Let O= makes handle a relative path with -C option" failed to apply to 4.9-stable tree
Date: Mon, 30 Mar 2020 11:39:47 -0400 [thread overview]
Message-ID: <20200330153947.GG4189@sasha-vm> (raw)
In-Reply-To: <1585570296177156@kroah.com>
On Mon, Mar 30, 2020 at 02:11:36PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.9-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From be40920fbf1003c38ccdc02b571e01a75d890c82 Mon Sep 17 00:00:00 2001
>From: Masami Hiramatsu <mhiramat@kernel.org>
>Date: Sat, 7 Mar 2020 03:32:58 +0900
>Subject: [PATCH] tools: Let O= makes handle a relative path with -C option
>
>When I tried to compile tools/perf from the top directory with the -C
>option, the O= option didn't work correctly if I passed a relative path:
>
> $ make O=BUILD -C tools/perf/
> make: Entering directory '/home/mhiramat/ksrc/linux/tools/perf'
> BUILD: Doing 'make -j8' parallel build
> ../scripts/Makefile.include:4: *** O=/home/mhiramat/ksrc/linux/tools/perf/BUILD does not exist. Stop.
> make: *** [Makefile:70: all] Error 2
> make: Leaving directory '/home/mhiramat/ksrc/linux/tools/perf'
>
>The O= directory existence check failed because the check script ran in
>the build target directory instead of the directory where I ran the make
>command.
>
>To fix that, once change directory to $(PWD) and check O= directory,
>since the PWD is set to where the make command runs.
>
>Fixes: c883122acc0d ("perf tools: Let O= makes handle relative paths")
>Reported-by: Randy Dunlap <rdunlap@infradead.org>
>Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
>Cc: Andrew Morton <akpm@linux-foundation.org>
>Cc: Borislav Petkov <bp@alien8.de>
>Cc: Geert Uytterhoeven <geert@linux-m68k.org>
>Cc: Jiri Olsa <jolsa@redhat.com>
>Cc: Masahiro Yamada <masahiroy@kernel.org>
>Cc: Michal Marek <michal.lkml@markovi.net>
>Cc: Peter Zijlstra <peterz@infradead.org>
>Cc: Sasha Levin <sashal@kernel.org>
>Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
>Cc: stable@vger.kernel.org
>Link: http://lore.kernel.org/lkml/158351957799.3363.15269768530697526765.stgit@devnote2
>Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Context conflicts with license changes... Fixed and queued up.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-03-30 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 12:11 FAILED: patch "[PATCH] tools: Let O= makes handle a relative path with -C option" failed to apply to 4.9-stable tree gregkh
2020-03-30 15:39 ` Sasha Levin [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=20200330153947.GG4189@sasha-vm \
--to=sashal@kernel.org \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jolsa@redhat.com \
--cc=masahiroy@kernel.org \
--cc=mhiramat@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stable@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