linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: bamvor.zhangjian@linaro.org, aneesh.kumar@linux.vnet.ibm.com,
	linux-kselftest@vger.kernel.org, shuahkh@osg.samsung.com
Subject: Re: selftests/powerpc: Fix standalone powerpc build
Date: Fri, 31 Mar 2017 23:35:30 +1100 (AEDT)	[thread overview]
Message-ID: <3vvgvQ3mb7z9s0g@ozlabs.org> (raw)
In-Reply-To: <1490588387-18903-1-git-send-email-mpe@ellerman.id.au>

On Mon, 2017-03-27 at 04:19:47 UTC, Michael Ellerman wrote:
> The changes to enable building with a separate output directory, in
> commit a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT") broke
> building the powerpc selftests on their own, eg:
> 
>  $ cd tools/testing/selftests/powerpc; make
> 
> It was partially fixed in commit e53aff45c490 ("selftests: lib.mk Fix
> individual test builds"), which defined OUTPUT for standalone tests. But
> that only defines OUTPUT within the Makefile, the value is not exported
> so sub-shells can't see it. We could export OUTPUT, but it's actually
> cleaner to just expand the value of OUTPUT before we invoke the shell.
> 
> Fixes: a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT")
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>

Applied to powerpc fixes.

https://git.kernel.org/powerpc/c/2db2c250dd3d1e74a50d4ab5f44c44

cheers

      reply	other threads:[~2017-03-31 12:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27  4:19 [PATCH] selftests/powerpc: Fix standalone powerpc build Michael Ellerman
2017-03-31 12:35 ` Michael Ellerman [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=3vvgvQ3mb7z9s0g@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=bamvor.zhangjian@linaro.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=shuahkh@osg.samsung.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;
as well as URLs for NNTP newsgroup(s).