trinity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <dborkman@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: trinity@vger.kernel.org
Subject: Re: stupid Q : how can I derive your patch from the trinity list
Date: Mon, 27 May 2013 10:21:49 +0200	[thread overview]
Message-ID: <51A3179D.7010801@redhat.com> (raw)
In-Reply-To: <51A22483.9040903@gmx.de>

On 05/26/2013 05:04 PM, Toralf Förster wrote:
> On 05/26/2013 04:51 PM, Daniel Borkmann wrote:
>> If you add an #include <linux/types.h> into trinity.h before gc.h
>> is included?
>>
>
> This doesn't help:

Ok, I compiled this against a 3.6.9-2.fc17.x86_64. So let me check this
on the latest net.git kernel.

gc.h seems to be innocent here, might be an issue with sigcontext.h
itself, e.g.:

   http://lists.openbios.org/pipermail/openbios/2012-June/006924.html

Let me check and come back to you.

> diff --git a/include/trinity.h b/include/trinity.h
> index b0dc2f8..fb42036 100644
> --- a/include/trinity.h
> +++ b/include/trinity.h
> @@ -2,6 +2,7 @@
>   #define _TRINITY_H 1
>
>   #define GC_THREADS
> +#include <linux/types.h>
>   #include <gc.h>
>
>   #include "types.h"
> lines 1-12/12 (END)
>
>

  reply	other threads:[~2013-05-27  8:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51A1E8DB.10000@gmx.de>
     [not found] ` <51A1FE73.2070807@redhat.com>
     [not found]   ` <51A2045D.1000402@gmx.de>
     [not found]     ` <51A207AB.7010706@gmx.de>
     [not found]       ` <51A20828.4070001@redhat.com>
2013-05-26 14:33         ` stupid Q : how can I derive your patch from the trinity list Toralf Förster
2013-05-26 14:51           ` Daniel Borkmann
2013-05-26 15:04             ` Toralf Förster
2013-05-27  8:21               ` Daniel Borkmann [this message]
2013-05-28 19:36                 ` Daniel Borkmann
2013-05-28 20:12                   ` Toralf Förster
2013-05-28 21:29                     ` Daniel Borkmann

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=51A3179D.7010801@redhat.com \
    --to=dborkman@redhat.com \
    --cc=toralf.foerster@gmx.de \
    --cc=trinity@vger.kernel.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 NNTP newsgroup(s).