From: Randy Dunlap <rdunlap@infradead.org>
To: Peter Foley <pefoley2@pefoley.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the rd-docs tree
Date: Tue, 16 Sep 2014 16:38:37 -0700 [thread overview]
Message-ID: <5418C9FD.1090400@infradead.org> (raw)
In-Reply-To: <CAOFdcFOXQRmxFQV_ei3xcdRLaCxEa4yjc=s=xjNM6R3SQBySgg@mail.gmail.com>
On 09/16/14 16:18, Peter Foley wrote:
> On Tue, Sep 16, 2014 at 7:00 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> Hi Peter,
>>
>> My build machine runs Debian stable which only has libc6 version 2.13.
>
> Ok, depending on a specific glibc version seems kinda hacky.
> Maybe we should just disable auto-building vdso_test?
>
> Randy?
> --
I don't have a good answer to that, so yes, I suppose just
disable it. Please send a patch.
Thanks,
--
~Randy
next prev parent reply other threads:[~2014-09-16 23:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 7:11 linux-next: build failure after merge of the rd-docs tree Stephen Rothwell
2014-09-16 17:19 ` Peter Foley
2014-09-16 23:00 ` Stephen Rothwell
2014-09-16 23:18 ` Peter Foley
2014-09-16 23:38 ` Randy Dunlap [this message]
2014-09-17 0:02 ` Peter Foley
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=5418C9FD.1090400@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pefoley2@pefoley.com \
--cc=sfr@canb.auug.org.au \
/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