Re: [RFC PATCH] UAPI: Document auxvec AT_* namespace policy and note reservations

Hi, Le mercredi 16 mai 2018 à 15:20 +0100, Dave Martin a écrit : > There are constraints on defining AT_* auxvec tags that are not > obvious to the casual maintainer of either the global > or the arch-specific headers. This is likely > to lead to mistakes. (I certainly fell foul of it...) > >

Re: [RFC PATCH] UAPI: Document auxvec AT_* namespace policy and note reservations

Hi, Le mercredi 16 mai 2018 à 15:20 +0100, Dave Martin a écrit : > There are constraints on defining AT_* auxvec tags that are not > obvious to the casual maintainer of either the global > or the arch-specific headers. This is likely > to lead to mistakes. (I certainly fell foul of it...) > >

Re: [RFC PATCH] UAPI: Document auxvec AT_* namespace policy and note reservations

Dave Martin writes: > There are constraints on defining AT_* auxvec tags that are not > obvious to the casual maintainer of either the global > or the arch-specific headers. This is likely > to lead to mistakes. (I certainly fell foul of it...) Thanks for cleaning this

Re: [RFC PATCH] UAPI: Document auxvec AT_* namespace policy and note reservations

Dave Martin writes: > There are constraints on defining AT_* auxvec tags that are not > obvious to the casual maintainer of either the global > or the arch-specific headers. This is likely > to lead to mistakes. (I certainly fell foul of it...) Thanks for cleaning this up. It looks like us

Re: [RFC PATCH] UAPI: Document auxvec AT_* namespace policy and note reservations

On Wed, May 16, 2018 at 04:09:29PM -0700, H. Peter Anvin wrote: > On 05/16/18 08:49, Dave Martin wrote: > > > > Since only contains #defines, it may be enough for arch > > headers to include . > > > > doesn't seem to have any reason to exist at all. If > anyone includes it now, they are

Re: [RFC PATCH] UAPI: Document auxvec AT_* namespace policy and note reservations

On Wed, May 16, 2018 at 04:09:29PM -0700, H. Peter Anvin wrote: > On 05/16/18 08:49, Dave Martin wrote: > > > > Since only contains #defines, it may be enough for arch > > headers to include . > > > > doesn't seem to have any reason to exist at all. If > anyone includes it now, they are

Re: [RFC PATCH] UAPI: Document auxvec AT_* namespace policy and note reservations

On 05/16/18 08:49, Dave Martin wrote: > > Since only contains #defines, it may be enough for arch > headers to include . > doesn't seem to have any reason to exist at all. If anyone includes it now, they are Doing It Wrong[TM] since includes . -hpa

Re: [RFC PATCH] UAPI: Document auxvec AT_* namespace policy and note reservations

On 05/16/18 08:49, Dave Martin wrote: > > Since only contains #defines, it may be enough for arch > headers to include . > doesn't seem to have any reason to exist at all. If anyone includes it now, they are Doing It Wrong[TM] since includes . -hpa

Re: [RFC PATCH] UAPI: Document auxvec AT_* namespace policy and note reservations

On Wed, May 16, 2018 at 11:29:13AM -0400, Rich Felker wrote: > On Wed, May 16, 2018 at 03:20:47PM +0100, Dave Martin wrote: > > There are constraints on defining AT_* auxvec tags that are not > > obvious to the casual maintainer of either the global > > or the arch-specific headers. This is

Re: [RFC PATCH] UAPI: Document auxvec AT_* namespace policy and note reservations

On Wed, May 16, 2018 at 11:29:13AM -0400, Rich Felker wrote: > On Wed, May 16, 2018 at 03:20:47PM +0100, Dave Martin wrote: > > There are constraints on defining AT_* auxvec tags that are not > > obvious to the casual maintainer of either the global > > or the arch-specific headers. This is

Re: [RFC PATCH] UAPI: Document auxvec AT_* namespace policy and note reservations

On Wed, May 16, 2018 at 03:20:47PM +0100, Dave Martin wrote: > There are constraints on defining AT_* auxvec tags that are not > obvious to the casual maintainer of either the global > or the arch-specific headers. This is likely > to lead to mistakes. (I certainly fell foul of it...) > > For

Re: [RFC PATCH] UAPI: Document auxvec AT_* namespace policy and note reservations

On Wed, May 16, 2018 at 03:20:47PM +0100, Dave Martin wrote: > There are constraints on defining AT_* auxvec tags that are not > obvious to the casual maintainer of either the global > or the arch-specific headers. This is likely > to lead to mistakes. (I certainly fell foul of it...) > > For