From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH] tools/libxl: remove O_CLOEXEC in xl_cmdimpl.c
Date: Tue, 21 Jun 2011 17:14:03 +0200 [thread overview]
Message-ID: <4E00B53B.2050407@amd.com> (raw)
In-Reply-To: <19968.43861.322213.458826@mariner.uk.xensource.com>
The applied version looks like to be a OS specific workaround.
NetBSD has O_CLOEXEC.
Christoph
On 06/21/11 16:31, Ian Jackson wrote:
> Ren, Yongjie writes ("[Xen-devel] [PATCH] tools/libxl: remove O_CLOEXEC in xl_cmdimpl.c"):
>> Hi all,
>> Some old linux kernel such as 2.6.18 which rhel5u5 natively
>> used haven't defined O_CLOEXEC, so remove O_CLOEXEC in xl_cmdimpl.c
>>
>> Signed-off-by: Yongjie Ren<yongjie.ren@intel.com>
>
> Acked-by: Ian Jackson<ian.jackson@eu.citrix.com>
> Committed-by: Ian Jackson<ian.jackson@eu.citrix.com>
>
> Thanks,
> Ian.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2011-06-21 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 6:29 make tools ERROR in latest xen-unstable.hg Ren, Yongjie
2011-06-17 7:01 ` Vincent Hanquez
2011-06-17 7:58 ` Zhang, Yang Z
2011-06-17 8:12 ` Vincent Hanquez
2011-06-20 14:29 ` make tools ERROR in latest xen-unstable.hg [and 1 more messages] Ian Jackson
2011-06-21 7:28 ` [PATCH] tools/libxl: remove O_CLOEXEC in xl_cmdimpl.c Ren, Yongjie
2011-06-21 14:31 ` Ian Jackson
2011-06-21 15:14 ` Christoph Egger [this message]
2011-06-21 15:20 ` Ian Jackson
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=4E00B53B.2050407@amd.com \
--to=christoph.egger@amd.com \
--cc=xen-devel@lists.xensource.com \
/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.