public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman•id.au>
To: Harish <harish@linux•ibm.com>, linuxppc-dev@lists•ozlabs.org
Cc: Harish <harish@linux•ibm.com>
Subject: Re: [RESEND][PATCH] selftests/vm: Fix vm tests build and run
Date: Mon, 10 Feb 2020 20:50:05 +1100	[thread overview]
Message-ID: <871rr222lu.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20200210073521.14117-1-harish@linux.ibm.com>

Harish <harish@linux•ibm.com> writes:
> A recent change overrides the ARCH env variable and hence runs
> using make fails with the following.
>
> $ make -C vm/
> make: Entering directory '/home/harish/linux/tools/testing/selftests/vm'
> make --no-builtin-rules ARCH=ppc64le -C ../../../.. headers_install
> make[1]: Entering directory '/home/harish/linux'
> Makefile:652: arch/ppc64le/Makefile: No such file or directory
> make[1]: *** No rule to make target 'arch/ppc64le/Makefile'.  Stop.
> make[1]: Leaving directory '/home/harish/linux'
> make: *** [../lib.mk:50: khdr] Error 2
> make: Leaving directory '/home/harish/linux/tools/testing/selftests/vm'
>
> Patch fixes this issue and also handles ppc64/ppc64le archs to enable
> few tests
>
> Signed-off-by: Harish <harish@linux•ibm.com>
> ---
>  tools/testing/selftests/vm/Makefile    | 4 ++--
>  tools/testing/selftests/vm/run_vmtests | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)

I don't maintain the vm tests. You need to send the patch to the right
people.

But as Christophe points out I think Sandipan has already done that.

cheers

      parent reply	other threads:[~2020-02-10  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10  7:35 [RESEND][PATCH] selftests/vm: Fix vm tests build and run Harish
2020-02-10  8:05 ` Christophe Leroy
2020-02-10  9:50 ` 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=871rr222lu.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman$(echo .)id.au \
    --cc=harish@linux$(echo .)ibm.com \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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