From: Joe Lawrence <email@example.com> To: shuah <firstname.lastname@example.org>, Yauheni Kaliuta <email@example.com>, Masahiro Yamada <firstname.lastname@example.org> Cc: email@example.com, firstname.lastname@example.org Subject: Re: kselftest OOT run_tests Date: Tue, 26 May 2020 16:40:06 -0400 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On 5/26/20 1:13 PM, 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. Also make M= doesn't make sense for them. > > 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? > Hey Yauheni, can you CC me on the use-case explanation? We currently do something really silly for the livepatch selftests on RHEL-7 for CKI that requires building them as pseudo OOT... in our case, we'd like to just be able to do something like make modules_prepare && make M= lib/livepatch, so perhaps a bit different... but I'd be curious for which problem you're currently trying to solve. Regards, -- Joe
next prev parent reply other threads:[~2020-05-26 20:40 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 [this message] 2020-05-27 7:34 ` Yauheni Kaliuta 2020-05-27 7:30 ` Yauheni Kaliuta 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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).