public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: shuah <shuah@kernel.org>
To: Dmitry Safonov <dima@arista.com>,
	linux-kselftest@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Aleksa Sarai <cyphar@cyphar.com>, Andrei Vagin <avagin@gmail.com>,
	shuah <shuah@kernel.org>
Subject: Re: Linux 5.6-rc1 kselftest build failures
Date: Wed, 12 Feb 2020 11:16:49 -0700	[thread overview]
Message-ID: <c191597b-c12e-9d06-01a3-7a7dda4f124f@kernel.org> (raw)
In-Reply-To: <c31e468a-3afe-f9b6-b006-c3bc3f35f1cc@arista.com>

On 2/12/20 7:09 AM, Dmitry Safonov wrote:
> Hi Shuah,
> 
> On 2/12/20 12:35 AM, shuah wrote:
>> The following tests fail to build on x86_64
> [..]
>> timerns:
>>
>> tools/testing/selftests/timens'
>> gcc -Wall -Werror -pthread  -lrt -ldl  timens.c  -o
>> tools/testing/selftests/timens/timens
>> /usr/bin/ld: /tmp/ccGy5CST.o: in function `check_config_posix_timers':
>> timens.c:(.text+0x65a): undefined reference to `timer_create'
>> collect2: error: ld returned 1 exit status
> 
> I've just send a patch to fix it:
> https://lkml.kernel.org/r/20200212140040.126747-1-dima@arista.com
> 
> Could you try it?

Yup. Works, responsed to the patch thread.

> 
> Also, it seems that the same thing affects futex/rtc/tcp_mmap/tcp_inq tests?
> 
> While looking into this, I see there are new auto-generated lkmdtm &&
> pidfd tests, is it worth to add them to .gitignore?
> 

Thanks for finding. Yes please send a patch for this.

thanks,
-- Shuah

      reply	other threads:[~2020-02-12 18:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12  0:35 Linux 5.6-rc1 kselftest build failures shuah
2020-02-12  8:14 ` Aleksa Sarai
2020-02-12 17:38   ` shuah
2020-02-13  7:27     ` Aleksa Sarai
2020-02-12 14:09 ` Dmitry Safonov
2020-02-12 18:16   ` shuah [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=c191597b-c12e-9d06-01a3-7a7dda4f124f@kernel.org \
    --to=shuah@kernel.org \
    --cc=avagin@gmail.com \
    --cc=cyphar@cyphar.com \
    --cc=dima@arista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.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