All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] containers/netns: fix header file path for	check_netns_enabled.c
Date: Thu, 6 Mar 2014 10:05:08 -0500 (EST)	[thread overview]
Message-ID: <115590897.213936.1394118308156.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1394117640-14933-1-git-send-email-liuhangbin@gmail.com>



----- Original Message -----
> From: "Hangbin Liu" <liuhangbin@gmail.com>
> To: ltp-list@lists.sourceforge.net
> Sent: Thursday, 6 March, 2014 3:54:00 PM
> Subject: [LTP] [PATCH] containers/netns: fix header file path for	check_netns_enabled.c
> 
> CLONE_NEWNET and CLONE_NEWNS are defined in linux/sched.h, not sched.h

/usr/include/bits/sched.h:# define CLONE_NEWNS   0x00020000 /* Set to create new namespace.  */
sched.h includes bits/sched.h

Where (distro, glibc version) do you see this fail when you include only sched.h?

Regards,
Jan

> 
> Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
> ---
>  testcases/kernel/containers/netns/check_netns_enabled.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/testcases/kernel/containers/netns/check_netns_enabled.c
> b/testcases/kernel/containers/netns/check_netns_enabled.c
> index ab8ee2f..7bb2324 100644
> --- a/testcases/kernel/containers/netns/check_netns_enabled.c
> +++ b/testcases/kernel/containers/netns/check_netns_enabled.c
> @@ -20,7 +20,7 @@
>  * when trying to use CLONE_NEWNET and CLONE_NEWNS.
>  ***************************************************************************/
>  #include <stdio.h>
> -#include <sched.h>
> +#include <linux/sched.h>
>  #include "config.h"
>  #include "libclone.h"
>  #include "linux_syscall_numbers.h"
> --
> 1.8.1.4
> 
> 
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries.  Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
> 

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2014-03-06 15:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 14:54 [LTP] [PATCH] containers/netns: fix header file path for check_netns_enabled.c Hangbin Liu
2014-03-06 15:05 ` Jan Stancek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-06  8:55 Hangbin Liu

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=115590897.213936.1394118308156.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=liuhangbin@gmail.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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.