From: "Usama" <usama.anjum@collabora.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: usama.anjum@collabora.com, Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
Shuah Khan <shuah@kernel.org>,
KERNEL SELFTEST FRAMEWORK <linux-kselftest@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"kernelci@groups.io" <kernelci@groups.io>
Subject: Re: [Bug Report] - kselftest build fails if output directory is first level sub-directory
Date: Mon, 27 Jun 2022 12:06:36 +0500 [thread overview]
Message-ID: <519c813b-0bf1-636b-df90-890e07d2ea4d@collabora.com> (raw)
In-Reply-To: <a9470bfc-bddc-6aa6-0043-d49eb57611fe@linuxfoundation.org>
>> This problem starts from the bad design of the kselftest framework.
>> I did some research before. I think I can fix the root cause but
>> currently I do not have enough time to do it.
>>
>>
>> KBUILD_ABS_SRCTREE is a user-interface to request
>> Kbuild to use the absolute path.
>> If it is forced in the top Makefile, users have no way to
>> negate it.
>> It is true that using the absolute path is a quick work-around
>> because you do not need to care about the current working directory.
>>
>> If you insist on it, just go ahead. It is just two line changes.
>> Once the issue is fixed in a better way, your patch can be reverted
>> easily.
>>
> Why don't we work on fixing it the wright way? I would rather go that
> route than using short rem fixes.
>
> Usama, would you be interested in working on a proper fix as recommended
> by Masahiro?
I've made another attempt:
https://lore.kernel.org/lkml/20220627070214.432390-1-usama.anjum@collabora.com/
>
> thanks,
> -- Shuah
--
Muhammad Usama Anjum
prev parent reply other threads:[~2022-06-27 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 6:44 [Bug Report] - kselftest build fails if output directory is first level sub-directory Usama
2022-05-22 17:15 ` Masahiro Yamada
2022-05-23 9:40 ` Usama
2022-06-07 12:59 ` Usama
2022-06-07 21:39 ` Shuah Khan
2022-06-27 7:06 ` Usama [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=519c813b-0bf1-636b-df90-890e07d2ea4d@collabora.com \
--to=usama.anjum@collabora.com \
--cc=kernelci@groups.io \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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