All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Kees Cook <keescook@google.com>
Cc: "Ted Ts'o" <tytso@mit.edu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Correct way to include siginfo.h?
Date: Thu, 29 Mar 2012 11:14:38 -0700	[thread overview]
Message-ID: <4F74A68E.9060202@zytor.com> (raw)
In-Reply-To: <CAGXu5jKaHygqzfbtahSBCM=EQmqkS8br5ndnLp0QCRFaka11SA@mail.gmail.com>

On 03/29/2012 11:13 AM, Kees Cook wrote:
> 
> We'll have to poke the glibc folks. In the meantime, Will Drewry found
> a stable way to handle this. Just make the first set of includes and
> defines be:
> 

Well, "recent events" hopefully make that a bit easier.

	-hpa


      reply	other threads:[~2012-03-29 18:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 17:01 Correct way to include siginfo.h? Kees Cook
2012-03-27 17:21 ` Ted Ts'o
2012-03-27 17:29   ` Kees Cook
2012-03-27 17:37     ` Ted Ts'o
2012-03-27 18:01       ` Kees Cook
2012-03-29 17:58         ` H. Peter Anvin
2012-03-29 18:13           ` Kees Cook
2012-03-29 18:14             ` H. Peter Anvin [this message]

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=4F74A68E.9060202@zytor.com \
    --to=hpa@zytor.com \
    --cc=keescook@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.