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...)
>
>
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 (
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 Doing
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
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 likel
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 t
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 the benefit of future maintainers, this patch collects the
relevant inform
7 matches
Mail list logo