From: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: Bamvor Jian Zhang
<bamvor.zhangjian-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Michael Ellerman <mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Shuah Khan <shuahkh-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>,
Tyler Baker <tyler.baker-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
dvhart-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Subject: Re: [RFD] How to support KBUILD_OUTPUT for kselftest?
Date: Tue, 26 Jan 2016 11:47:40 -0800 [thread overview]
Message-ID: <7hk2mwnmw3.fsf@baylibre.com> (raw)
In-Reply-To: <56849D4B.6010008-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> (Bamvor Jian Zhang's message of "Thu, 31 Dec 2015 11:13:15 +0800")
Bamvor Jian Zhang <bamvor.zhangjian-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> writes:
> I am trying to improve cross compiling support for kselftest recently. Right
> now I am stuck when I want to enable KBUILD_OUTPUT(O=xxx). It exist in wiki of
> kselftest[1]. Hope it is not a duplicated work.
Just want to echo the need for this feature because trying to build
kselftests for a kernel built with KBUILD_OUTPUT is broken due to
hard-coded assumptions about paths to headers, etc.
I haven't dug any deeper into how to fix it though...
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Bamvor Jian Zhang <bamvor.zhangjian@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-api@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
Mark Brown <broonie@kernel.org>,
Shuah Khan <shuahkh@osg.samsung.com>,
Tyler Baker <tyler.baker@linaro.org>,
dvhart@infradead.org
Subject: Re: [RFD] How to support KBUILD_OUTPUT for kselftest?
Date: Tue, 26 Jan 2016 11:47:40 -0800 [thread overview]
Message-ID: <7hk2mwnmw3.fsf@baylibre.com> (raw)
In-Reply-To: <56849D4B.6010008@linaro.org> (Bamvor Jian Zhang's message of "Thu, 31 Dec 2015 11:13:15 +0800")
Bamvor Jian Zhang <bamvor.zhangjian@linaro.org> writes:
> I am trying to improve cross compiling support for kselftest recently. Right
> now I am stuck when I want to enable KBUILD_OUTPUT(O=xxx). It exist in wiki of
> kselftest[1]. Hope it is not a duplicated work.
Just want to echo the need for this feature because trying to build
kselftests for a kernel built with KBUILD_OUTPUT is broken due to
hard-coded assumptions about paths to headers, etc.
I haven't dug any deeper into how to fix it though...
Kevin
next prev parent reply other threads:[~2016-01-26 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 3:13 [RFD] How to support KBUILD_OUTPUT for kselftest? Bamvor Jian Zhang
[not found] ` <56849D4B.6010008-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-01-26 19:47 ` Kevin Hilman [this message]
2016-01-26 19:47 ` Kevin Hilman
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=7hk2mwnmw3.fsf@baylibre.com \
--to=khilman-rdvid1duhrbwk0htik3j/w@public.gmane.org \
--cc=bamvor.zhangjian-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=dvhart-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org \
--cc=shuahkh-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org \
--cc=tyler.baker-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.