public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH 1/2] nptl: Remove __ASSUME_SET_ROBUST_LIST
Date: Wed, 19 Apr 2017 14:52:00 -0000	[thread overview]
Message-ID: <e4d07239-1591-8d59-7c51-ac888eeed183@linaro.org> (raw)
In-Reply-To: <87pog85u3c.fsf@linux-m68k.org>



On 19/04/2017 11:51, Andreas Schwab wrote:
> On Apr 19 2017, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:
> 
>> * m68k Uses the default include/asm-generic/futex.h which only has support for
>>   uniprocessors.
> 
> m68k has no support for SMP.
> 
> Andreas.
> 

Right, so m68k should be safe regarding robust support (assuming asm-generic/futex.h
works correctly).

  reply	other threads:[~2017-04-19 14:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 21:13 Adhemerval Zanella
2017-04-18 21:13 ` [PATCH 2/2] linux: Remove __ASSUME_SET_ROBUST_LIST defines Adhemerval Zanella
2017-04-19  5:37 ` [PATCH 1/2] nptl: Remove __ASSUME_SET_ROBUST_LIST Florian Weimer
2017-04-19 14:18   ` Adhemerval Zanella
2017-04-19 14:51     ` Andreas Schwab
2017-04-19 14:52       ` Adhemerval Zanella [this message]
2017-04-19 15:28     ` Florian Weimer
2017-04-19 17:38       ` Adhemerval Zanella
2017-04-19 18:09         ` Florian Weimer
2017-04-19 21:02           ` Adhemerval Zanella
2017-04-20 12:51           ` Adhemerval Zanella
2017-04-20 12:52             ` Florian Weimer
2017-04-20 13:09               ` Adhemerval Zanella
2017-04-20 13:47                 ` Florian Weimer
2017-04-20 17:25                   ` Adhemerval Zanella
  -- strict thread matches above, loose matches on Subject: below --
2016-09-21 14:11 Adhemerval Zanella

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=e4d07239-1591-8d59-7c51-ac888eeed183@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@linux-m68k.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).