public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] Synchronize <sys/personality.h> with kernel headers
Date: Fri, 25 Mar 2016 16:20:00 -0000	[thread overview]
Message-ID: <20160325161940.GC14337@aurel32.net> (raw)
In-Reply-To: <56F55F2B.4070108@linaro.org>

On 2016-03-25 12:54, Adhemerval Zanella wrote:
> LGTM. I wonder if you should include PER_CLEAR_ON_SETID as well, thoughts? 

I don't really know either. It is define upstream as a macro and not an
enum, I don't really know why.

Looking at codesearch.debian.net it doesn't seem to be use by userland,
contrary to the three others (though in very few places). So I would
rather got for not including it for now.

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

  reply	other threads:[~2016-03-25 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 18:36 Aurelien Jarno
2016-03-25 15:54 ` Adhemerval Zanella
2016-03-25 16:20   ` Aurelien Jarno [this message]
2016-03-25 16:41     ` 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=20160325161940.GC14337@aurel32.net \
    --to=aurelien@aurel32.net \
    --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).