bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
To: shuah <shuah@kernel.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
	linux-kselftest@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: kselftest OOT run_tests
Date: Wed, 27 May 2020 10:30:20 +0300	[thread overview]
Message-ID: <xunytv01omwj.fsf@redhat.com> (raw)
In-Reply-To: <ad5ee014-759c-d0fb-5dc1-f1f25481a453@kernel.org> (shuah@kernel.org's message of "Tue, 26 May 2020 11:13:29 -0600")

Hi, shuah!

>>>>> On Tue, 26 May 2020 11:13:29 -0600, shuah   wrote:

 > On 5/25/20 7:55 AM, Yauheni Kaliuta wrote:
 >> Hi!
 >> 
 >> I'm wondering how out of tree check is supposed to work for make
 >> O=dir run_tests from selftests (or make -C ...) directory?
 >> 
 >> (both with 051f278e9d81 ("kbuild: replace KBUILD_SRCTREE with
 >> boolean building_out_of_srctree") and without)
 >> 
 >> make M= ... does not work with run_tests.
 >> 

 > Kselftests run_tests target isn't intended for building and
 > running tests OOT.

But there is code there trying to handle it. All that OUTPUT
related things must be removed if it's broken, right? Can I post
a patch?

 > Also make M= doesn't make sense for them.

Well, M=... at least includes all the makefiles.

 > There is no support to build OOT at the moment. I would like
 > to get a better understanding of your use-case. Can you
 > elaborate?

I care about make install actually. But fixing it I had to deal
with OUTPUT. Looking a proper for that I found that it's a bit
broken.


-- 
WBR,
Yauheni Kaliuta


  parent reply	other threads:[~2020-05-27  7:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 13:55 Yauheni Kaliuta
2020-05-26 17:13 ` shuah
2020-05-26 20:40   ` Joe Lawrence
2020-05-27  7:34     ` Yauheni Kaliuta
2020-05-27  7:30   ` Yauheni Kaliuta [this message]
2020-05-27 18:22     ` shuah
2020-05-27 18:40       ` Yauheni Kaliuta
2020-05-27 21:46         ` shuah

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=xunytv01omwj.fsf@redhat.com \
    --to=yauheni.kaliuta@redhat.com \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=yamada.masahiro@socionext.com \
    --subject='Re: kselftest OOT run_tests' \
    /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

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).