Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] nilfs-utils: need NPTL threads
Date: Sun, 7 Jan 2018 21:08:29 +0100	[thread overview]
Message-ID: <20180107200829.GA30596@waldemar-brodkorb.de> (raw)
In-Reply-To: <20180105052334.mc3fabifliw7gzqn@tarshish>

Hi Baruch,
Baruch Siach wrote,

> The UCLIBC_HAS_ADVANCED_REALTIME help text says that this options enables 
> clock_nanosleep(). But with current code you must have NPTL enabled for 
> clock_nanosleep(). So the help text is not correct.
> 
> This also means that architectures lack NPTL support can't have 
> clock_nanosleep() at all. Is there a reason for that?

You are right. It seems there is no reason for it.
clock_nanosleep is internally using a syscall.

I prepared attached patch and running the regression tests.

Do you like to test or review?

I cleaned up old code, which might be only required for Linux
kernels older than 2.6.0, which I do not going to support anyway.

best regards
 Waldemar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0006-rt-cleanup-and-allow-to-build-for-linuxthreads.patch
Type: text/x-diff
Size: 11284 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180107/62b2ebc0/attachment.patch>

  parent reply	other threads:[~2018-01-07 20:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 10:10 [Buildroot] [PATCH 1/2] nilfs-utils: need NPTL threads Kurt Van Dijck
2018-01-04 10:10 ` [Buildroot] [PATCH 2/2] nilfs-utils: fix build with static toolchains Kurt Van Dijck
2018-01-06 14:47   ` Thomas Petazzoni
2018-01-06 20:30     ` Kurt Van Dijck
2018-01-04 10:19 ` [Buildroot] [PATCH 1/2] nilfs-utils: need NPTL threads Baruch Siach
2018-01-04 10:33   ` Thomas Petazzoni
2018-01-04 10:51     ` Baruch Siach
2018-01-04 11:28       ` Kurt Van Dijck
2018-01-04 15:52         ` Yann E. MORIN
2018-01-04 17:23           ` Baruch Siach
     [not found]             ` <20180104201958.GB5130@waldemar-brodkorb.de>
2018-01-05  5:23               ` Baruch Siach
2018-01-05 10:17                 ` Kurt Van Dijck
2018-01-05 10:31                   ` Thomas Petazzoni
2018-01-05 11:24                   ` Baruch Siach
2018-01-05 13:20                     ` Kurt Van Dijck
2018-01-05 14:03                       ` Baruch Siach
2018-01-07 20:08                 ` Waldemar Brodkorb [this message]
2018-01-05 19:56   ` Kurt Van Dijck
2018-01-06 14:35 ` Thomas Petazzoni
2018-01-06 20:32   ` Kurt Van Dijck

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=20180107200829.GA30596@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=buildroot@busybox.net \
    /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