From: Randy Dunlap <rdunlap@infradead.org>
To: Andy Lutomirski <luto@amacapital.net>,
Peter Foley <pefoley2@pefoley.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Chuck Ebbert <cebbert.lkml@gmail.com>,
Josh Boyer <jwboyer@fedoraproject.org>,
Jiri Kosina <jkosina@suse.cz>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: vdso_standalone_test_x86.c build failure on Linus' tree
Date: Wed, 08 Oct 2014 17:18:17 -0700 [thread overview]
Message-ID: <5435D449.5030403@infradead.org> (raw)
In-Reply-To: <CALCETrUCLw5si9S4LZT9dbO=UsftjJ63Q4vshfq3t=B2sywbZg@mail.gmail.com>
On 10/08/14 16:18, Andy Lutomirski wrote:
> On Wed, Oct 8, 2014 at 4:11 PM, Peter Foley <pefoley2@pefoley.com> wrote:
>> On Wed, Oct 8, 2014 at 5:21 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>>> That we can't solve, but it is not okay to break the kernel build.
>>
>> Should I just make CONFIG_BUILD_DOCSRC depend on CROSS_COMPILE=""?
>> I'm not sure how much value would be added by implementing targetprogs
>> in kbuild, simply to increase build testing of Documentation/
>
> Yes, IMO. Let the kselftest people solve it, because they might have
> extra requirements.
>
> --Andy
As I have said in the past, there are probably lots of source files in
Documentation/ that should be in tools/ or tools/testing/ instead.
--
~Randy
next prev parent reply other threads:[~2014-10-09 0:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 18:52 vdso_standalone_test_x86.c build failure on Linus' tree Josh Boyer
2014-10-08 19:16 ` Andy Lutomirski
2014-10-08 19:44 ` Peter Foley
2014-10-08 20:46 ` Chuck Ebbert
2014-10-08 20:50 ` Andy Lutomirski
2014-10-08 20:55 ` H. Peter Anvin
2014-10-08 21:09 ` Chuck Ebbert
2014-10-08 21:21 ` H. Peter Anvin
2014-10-08 23:08 ` Chuck Ebbert
2014-10-08 23:11 ` Peter Foley
2014-10-08 23:18 ` Andy Lutomirski
2014-10-09 0:18 ` Randy Dunlap [this message]
2014-10-08 21:21 ` Josh Boyer
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=5435D449.5030403@infradead.org \
--to=rdunlap@infradead.org \
--cc=cebbert.lkml@gmail.com \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pefoley2@pefoley.com \
--cc=torvalds@linux-foundation.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.