public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 1/2] Enable ILP32 mode on aarch64, update abilist files
Date: Wed, 30 Nov 2016 13:20:00 -0000	[thread overview]
Message-ID: <500a4419-41bc-7c14-82d3-ebc30438badd@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1611301259060.3647@digraph.polyomino.org.uk>



On 30/11/2016 11:00, Joseph Myers wrote:
> On Wed, 30 Nov 2016, Adhemerval Zanella wrote:
> 
>>> Possibly new comment: basing on top of Adhemerval's sysvipc consolidation 
>>> <https://sourceware.org/ml/libc-alpha/2016-11/msg00284.html> would be 
>>> better than adding new versions of various sysvipc files (if you think you 
>>> still need new versions after that patch, you need to work with Adhemerval 
>>> on making it more general).
>>
>> My understanding is, although not explicit state in this thread, ILP32
>> port is still based on my sysvipc consolidation (at least is what Yury
>> was working with on previous iterations).
> 
> The patch adds files msgctl.c, semctl.c and shmctl.c.  If it's based on 
> your series, I'd expect it not to include such files.

Right, for some reason the part 2/2 is not my local thread. I will reply
for that part.

  reply	other threads:[~2016-11-30 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 18:50 Steve Ellcey
2016-11-29 18:53 ` Steve Ellcey
2016-11-30  0:12 ` Joseph Myers
2016-11-30 12:24   ` Adhemerval Zanella
2016-11-30 13:01     ` Joseph Myers
2016-11-30 13:20       ` Adhemerval Zanella [this message]
2016-12-01  5:13     ` Yury Norov
2016-12-02 18:34   ` Steve Ellcey
2016-12-02 19:08     ` 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=500a4419-41bc-7c14-82d3-ebc30438badd@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.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).