From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] libxl: add missing includes
Date: Tue, 21 Feb 2012 10:18:39 +0100 [thread overview]
Message-ID: <4F43616F.9060902@amd.com> (raw)
In-Reply-To: <20290.38015.460233.816604@mariner.uk.xensource.com>
On 02/20/12 19:44, Ian Jackson wrote:
> Christoph Egger writes ("[Xen-devel] [PATCH] libxl: add missing includes"):
>>
>> include<poll.h> for struct pollfd
>> include<time.h> for struct timeval
>> Fixes gcc complaints about implicit declaration.
>
> According to SuS, it should be<sys/time.h>.
Yes, sorry. Should I resend?
Christoph
--
---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:[~2012-02-21 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 13:14 [PATCH] libxl: add missing includes Christoph Egger
2012-02-20 18:44 ` Ian Jackson
2012-02-21 9:18 ` Christoph Egger [this message]
2012-02-21 16:44 ` 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=4F43616F.9060902@amd.com \
--to=christoph.egger@amd.com \
--cc=Ian.Jackson@eu.citrix.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 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).